You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Improve native build concurrency enforcement with a clear customer-facing 429 that includes active build count, plan limit, plan name, and an upgrade URL.
Fail early on /build/request (before upload/job creation) and keep transactional enforcement on /build/start.
Persist concurrency failures on the build row so the dashboard shows the error + Upgrade CTA.
Update the Capgo CLI to print the upgrade message and open the plans page.
Emit Bento event user:native_build_concurrency_limit (preference usage_limit) for a later upgrade email automation.
Motivation (AI generated)
Pricing advertises concurrent native builds per plan, and the backend already had a hard gate at start time, but customers got a generic rate-limit style failure with no upgrade path, no dashboard persistence, no CLI guidance, and no Bento hook for follow-up email.
Business Impact (AI generated)
Protects builder capacity according to paid tiers while converting blocked builds into upgrade opportunities via CLI, dashboard, and a Bento-ready email event.
Visual changes (AI generated)
Dashboard build error row/dialog now exposes an Upgrade CTA when the failure is a plan/concurrency limit:
Test Plan (AI generated)
bunx vitest run tests/native-build-concurrency.unit.test.ts tests/build-request-plan-gate.unit.test.ts tests/build-start-log-token.test.ts
Lint / typecheck
CI unit, DB, backend (both shards), Cloudflare (both shards), CLI suite (on prior green run)
CodeRabbit review comments addressed and resolved
Wire Bento automation for user:native_build_concurrency_limit when email is ready
Generated with AI
Summary by CodeRabbit
New Features
Added native build concurrency protection to prevent builds from exceeding plan limits.
Added clear error messages with current limits and direct links to upgrade plans.
Added upgrade actions in build error dialogs and build tables.
Builds blocked by concurrency limits now fail cleanly and provide actionable guidance.
Documentation
Updated usage-limit alert setup guidance to include native build concurrency notifications.
Enforce plan concurrent-build limits with a clear customer error, upgrade
link, dashboard failed-build persistence, CLI handling, and a Bento event
for follow-up email automations.
Co-authored-by: Martin DONADIEU <martindonadieu@gmail.com>
Your recent review volume is higher than typical usage, so adaptive limits are currently applied.
Next review available in:19 minutes
Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).
How can I continue?
After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.
To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.
How do review limits work?
CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.
For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.
Native build concurrency enforcement is centralized across backend request and startup flows, with standardized 429 errors, upgrade URLs, telemetry, CLI handling, web upgrade navigation, tests, and Bento event documentation.
Changes
Native build concurrency flow
Layer / File(s)
Summary
Centralized concurrency state and enforcement supabase/functions/_backend/public/build/concurrency.ts, tests/native-build-concurrency.unit.test.ts
Adds shared concurrency state, plan-limit checks, upgrade URL and error helpers, telemetry notifications, request prechecks, and standardized reservation failures with expanded coverage.
Build request and startup integration supabase/functions/_backend/public/build/request.ts, supabase/functions/_backend/public/build/start.ts, tests/build-request-plan-gate.unit.test.ts, tests/build-start-log-token.test.ts
Checks concurrency before builder job creation, includes upgrade metadata in plan errors, and marks builds failed when startup reservation reaches the concurrency limit.
CLI and web upgrade actions cli/src/build/request.ts, src/components/tables/BuildTable.vue, docs/BENTO_EMAIL_PREFERENCES_SETUP.md
Parses and surfaces 429 upgrade errors in the CLI, adds plan navigation in build error UI, and documents the native-build concurrency Bento event.
No successful run was found on main (7e18610) during the generation of this report, so 42b818a was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩
The reason will be displayed to describe this comment to others. Learn more.
Stale comment
Risk: high. Cursor Bugbot did not complete (check skipped due to usage limit), so automated review is unavailable for this billing-sensitive build concurrency change. Human review is required; reviewers assigned.
Sent by Cursor Approval Agent: Pull Request Approver External
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 6
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@cli/src/build/request.ts`:
- Around line 230-266: Update throwIfBuildPlanLimitError to await the dynamic
import and browser-opening call, while preserving the existing catch that
ignores open failures. Remove reliance on the trailing wait as synchronization
so the upgrade URL opening completes before the function waits and throws.
In `@docs/BENTO_EMAIL_PREFERENCES_SETUP.md`:
- Around line 49-52: Update the “Filter to add” section in
BENTO_EMAIL_PREFERENCES_SETUP.md by inserting a blank line between the heading
text and the fenced code block, keeping the filter content unchanged.
In `@src/components/tables/BuildTable.vue`:
- Around line 196-201: Rename isNativeBuildConcurrencyError to reflect that it
also classifies plan-upgrade errors, such as isPlanUpgradeError, and update all
call sites accordingly; or remove the /settings/organization/plans match if only
native-build concurrency errors should be recognized.
- Around line 396-402: Add an explicit non-submitting type attribute to the
button rendered when isNativeBuildConcurrencyError(element.last_error) in
BuildTable, preserving its existing click navigation behavior.
In `@supabase/functions/_backend/public/build/concurrency.ts`:
- Around line 183-206: Verify that build_requests has an index supporting the
owner_org and active-status filtering used by countActiveNativeBuilds and the
related UPDATE query. If no suitable index exists, add the appropriate
migration/index and ensure both query paths can use it without changing their
behavior.
- Around line 212-245: Update assertNativeBuildConcurrencyAvailable to obtain
its PostgreSQL client with the read-only option enabled by passing true to
getPgClient(c). Keep reserveNativeBuildSlot and the existing transaction path
unchanged.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
Push a commit to this branch (recommended)
Create a new PR with the fixes
ℹ️ Review info⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: 5c702a2e-b283-4afc-ba5e-04614eb44ec6
📥 Commits
Reviewing files that changed from the base of the PR and between 7e18610 and d56c130.
Await CLI upgrade-URL open, clarify plan-upgrade dashboard classifier,
mark Upgrade button type=button, document org index for active-build
counts, and use a read-only PG client for the request precheck.
Co-authored-by: Martin DONADIEU <martindonadieu@gmail.com>
The reason will be displayed to describe this comment to others. Learn more.
Stale comment
Risk: medium. Not approving: Cursor Bugbot was skipped due to usage limits and did not complete analysis. Human reviewers (Dalanir, WcaleNieWolny) are already assigned.
Sent by Cursor Approval Agent: Pull Request Approver
The reason will be displayed to describe this comment to others. Learn more.
Stale comment
Risk: high. Not approving: Cursor Bugbot did not complete (check skipped due to usage limit), so automated review is unavailable for this billing-sensitive build concurrency change. Human review is required; two reviewers are already assigned.
Sent by Cursor Approval Agent: Pull Request Approver External
The reason will be displayed to describe this comment to others. Learn more.
Risk: high. Not approving: Cursor Bugbot did not complete (check skipped due to usage limit), so automated review is unavailable for this billing-sensitive build concurrency change. Human review is required; two reviewers are already assigned.
Sent by Cursor Approval Agent: Pull Request Approver External
The reason will be displayed to describe this comment to others. Learn more.
Risk: medium. Not approving: Cursor Bugbot was skipped (usage limit) and did not complete analysis. Human reviewers (Dalanir, WcaleNieWolny) are already assigned and the PR has human approval.
Sent by Cursor Approval Agent: Pull Request Approver
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
Summary (AI generated)
/build/request(before upload/job creation) and keep transactional enforcement on/build/start.user:native_build_concurrency_limit(preferenceusage_limit) for a later upgrade email automation.Motivation (AI generated)
Pricing advertises concurrent native builds per plan, and the backend already had a hard gate at start time, but customers got a generic rate-limit style failure with no upgrade path, no dashboard persistence, no CLI guidance, and no Bento hook for follow-up email.
Business Impact (AI generated)
Protects builder capacity according to paid tiers while converting blocked builds into upgrade opportunities via CLI, dashboard, and a Bento-ready email event.
Visual changes (AI generated)
Dashboard build error row/dialog now exposes an Upgrade CTA when the failure is a plan/concurrency limit:
Test Plan (AI generated)
bunx vitest run tests/native-build-concurrency.unit.test.ts tests/build-request-plan-gate.unit.test.ts tests/build-start-log-token.test.tsuser:native_build_concurrency_limitwhen email is readyGenerated with AI
Summary by CodeRabbit
New Features
Documentation