[MagMueller]

The general per-project request bucket (creates, lists, updates, deletes, event reads) is changing from a flat 25 RPS to max(25, 2 × stored concurrency) capped at 100 RPS, in browser-use/cloud#5909. Free and Tier 0 projects stay at 25 RPS, Tier 1 and above get 100 RPS, and higher general budgets remain account overrides. This updates the concurrency guide table, the worked example, the event-wait guidance and the docs.json agent context to match. Do not merge until cloud#5909 is deployed, so the docs never advertise a budget prod does not enforce yet.

🤖 Generated with Claude Code

https://claude.ai/code/session_01V46rG7LtFkrKKbxfEAM3U8

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
browser-use	🟢 Ready	View Preview	Sep 12, 2026, 6:51 AM

💡 Tip: Enable Automations to automatically generate PRs for you.

[cubic-dev-ai]

No issues found across 2 files

_{Re-trigger cubic}

[cubic-dev-ai]

1 issue found across 2 files (changes from recent commits).

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="docs/docs.json">

<violation number="1" location="docs/docs.json:1185">
P3: The rewritten sentence "The separate per-project application budgets: general traffic ... defaults to ...; selected status reads default to ..." is now an incomplete clause: "budgets" is a noun with no verb before the colon, so it reads as a fragment. The prior wording had a main verb ("The separate per-project application budgets both default to ..."). Add a verb or rephrase so the subject is resolved, e.g. "The separate per-project application budgets are independent: general traffic ... defaults to ..., while selected status reads default to ... with no cap."</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Fix all with cubic | Re-trigger cubic</sub>

[cubic-dev-ai]

P3: The rewritten sentence "The separate per-project application budgets: general traffic ... defaults to ...; selected status reads default to ..." is now an incomplete clause: "budgets" is a noun with no verb before the colon, so it reads as a fragment. The prior wording had a main verb ("The separate per-project application budgets both default to ..."). Add a verb or rephrase so the subject is resolved, e.g. "The separate per-project application budgets are independent: general traffic ... defaults to ..., while selected status reads default to ... with no cap."

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At docs/docs.json, line 1185:

<comment>The rewritten sentence "The separate per-project application budgets: general traffic ... defaults to ...; selected status reads default to ..." is now an incomplete clause: "budgets" is a noun with no verb before the colon, so it reads as a fragment. The prior wording had a main verb ("The separate per-project application budgets both default to ..."). Add a verb or rephrase so the subject is resolved, e.g. "The separate per-project application budgets are independent: general traffic ... defaults to ..., while selected status reads default to ... with no cap."</comment>

<file context>
@@ -1182,7 +1182,7 @@
       "Cloud concurrency and HTTP request rate are separate. Read GET /api/v2/billing/account for the key\u2019s projectId, concurrentSessionLimit, activeSessionCount, and credit balance, including when using V4. Keys in one project share capacity and credits; rateLimit is a legacy concurrency alias, not requests per second.",
       "Keep the highest applicable existing, legacy-plan, and spend-tier concurrency grant. Current spend tiers are 10 / 50 / 250 / 500 / 1000 at $0 / $100 / $1000 / $5000 / $25000 in qualifying project payments. Legacy or externally billed projects can follow different billing paths; trust the account limit. See https://docs.browser-use.com/cloud/guides/concurrency.md.",
-      "HTTP rate limits have two layers. Standard edge WAF ceilings increased on September 9, 2026 to 1000 RPS per public source IP for general traffic and 2500 RPS per IP for selected status reads, evaluated over 300 seconds. The separate per-project application budgets both default to max(25, 2 times stored concurrency): one bucket for general traffic including V4 events and full run reads, one for selected status reads, counted independently. Project overrides and account-specific edge rules can differ. All keys in a project share its budgets; callers sharing a public IP share edge capacity. See https://docs.browser-use.com/cloud/guides/concurrency.md.",
+      "HTTP rate limits have two layers. Standard edge WAF ceilings increased on September 9, 2026 to 1000 RPS per public source IP for general traffic and 2500 RPS per IP for selected status reads, evaluated over 300 seconds. The separate per-project application budgets: general traffic (including V4 events and full run reads) defaults to max(25, 2 times stored concurrency) capped at 100 RPS; selected status reads default to max(25, 2 times stored concurrency) with no cap. The two are counted independently. Project overrides and account-specific edge rules can differ. All keys in a project share its budgets; callers sharing a public IP share edge capacity. See https://docs.browser-use.com/cloud/guides/concurrency.md.",
       "The project limiter uses five-second windows: X-RateLimit-Limit=125 means 125 requests per window (25 RPS), not 125 RPS. Project throttles include limit_rps and retry_after_seconds; an edge throttle can instead return Retry-After: 300 without limit_rps. Honor the returned Retry-After. Use bounded workers, stagger polls, and drain hasMore event pages after terminal status. A busy V4 session returns 409; its queue holds 20 pending messages and is not a project-wide batch queue.",
       "A completed run or closed CDP connection does not immediately stop its cloud browser. Stop unneeded owned browsers with PATCH /api/v4/browsers/{id} and {\"action\":\"stop\"}. A client wait timeout does not cancel the server-side run.",
</file context>

Suggested change

"HTTP rate limits have two layers. Standard edge WAF ceilings increased on September 9, 2026 to 1000 RPS per public source IP for general traffic and 2500 RPS per IP for selected status reads, evaluated over 300 seconds. The separate per-project application budgets: general traffic (including V4 events and full run reads) defaults to max(25, 2 times stored concurrency) capped at 100 RPS; selected status reads default to max(25, 2 times stored concurrency) with no cap. The two are counted independently. Project overrides and account-specific edge rules can differ. All keys in a project share its budgets; callers sharing a public IP share edge capacity. See https://docs.browser-use.com/cloud/guides/concurrency.md.",

"HTTP rate limits have two layers. Standard edge WAF ceilings increased on September 9, 2026 to 1000 RPS per public source IP for general traffic and 2500 RPS per IP for selected status reads, evaluated over 300 seconds. The separate per-project application budgets are counted independently: general traffic (including V4 events and full run reads) defaults to max(25, 2 times stored concurrency) capped at 100 RPS, while selected status reads default to max(25, 2 times stored concurrency) with no cap. Project overrides and account-specific edge rules can differ. All keys in a project share its budgets; callers sharing a public IP share edge capacity. See https://docs.browser-use.com/cloud/guides/concurrency.md.",