Document unified concurrency limit (CUS-275)

[Jayko001]

Summary

Updates docs for the consolidation of the separate on-demand and browser-pool concurrency limits into a single unified concurrency limit (CUS-275, enforcement shipped in kernel/kernel#2540).

• info/pricing.mdx — replaces the separate "Reserved browsers" / "On-demand browsers" rows with a single "Concurrent browsers" row (5 / 10 / 150 / Custom), adds an intro explaining the unified limit, notes that reserved pool capacity counts toward the limit, and updates the Standby note.
• info/projects.mdx — rewrites the Concurrency Limits intro to describe the unified semantics (create + pool reservations share one cap), updates "concurrent-session limit" wording, and adds a deprecation note for max_pooled_sessions.
• reference/cli/projects.mdx — marks --max-pooled-sessions deprecated and clarifies --max-concurrent-sessions covers both.

API reference / SDK description updates are in a companion PR on kernel/kernel (openapi.yaml → Stainless).

⚠️ Do not merge yet

Draft until the kernel_api_unified_concurrency_limit flag is switched to on and affected customers with custom overrides have been notified. Merging early would document behavior most orgs don't have yet.

🤖 Generated with Claude Code

---

Note

Low Risk
Documentation-only changes with no runtime or security impact; merge timing should follow the feature flag rollout noted in the PR.

Overview
Documents one org-wide concurrency cap for on-demand browsers.create() and browser pool reservations, replacing the old split between reserved vs on-demand limits.

info/pricing.mdx adds an intro on the unified limit, collapses the plan table to a single Concurrent browsers row (Start-Up 150 vs the old 100 reserved + 50 on-demand), and clarifies that reserved pool size and Standby browsers both consume that cap.

info/projects.mdx rewrites concurrency semantics (sessions + pool slots share one org limit), updates API wording to “concurrency limit,” and notes max_pooled_sessions is deprecated (counts toward max_concurrent_sessions; setting it returns 400).

reference/cli/projects.mdx aligns --max-concurrent-sessions with the unified model and marks --max-pooled-sessions deprecated.

^{Reviewed by Cursor Bugbot for commit 3b8bcd9. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Stale comment

Risk assessment: Very Low

Evidence from the diff: this PR only edits three Mintlify documentation pages (info/pricing.mdx, info/projects.mdx, and reference/cli/projects.mdx) with 17 additions and 10 deletions. The changes update user-facing docs around the unified browser concurrency limit and deprecating pooled session wording; they don't modify application code, generated API schemas, infrastructure, auth/permissions, billing enforcement logic, or shared runtime behavior.

Approval note: the PR is already approved, so I'm leaving the required assessment comment without adding another approval.

  

_{Sent by Cursor Automation: Assign PR reviewers}

[cursor]

Risk assessment: Very Low

Evidence from the diff: this PR only changes three Mintlify documentation pages (info/pricing.mdx, info/projects.mdx, and reference/cli/projects.mdx) with 17 additions and 10 deletions. The edits update wording and tables for the unified browser concurrency limit, including how browser pools and deprecated pooled-session settings are described. They don't modify application code, generated API schemas, infrastructure, auth/permissions, billing enforcement logic, or shared runtime behavior.

Code ownership / approval note: I found no CODEOWNERS file in the checked-out repo, and the PR is already approved at the current head commit, so I'm leaving this assessment as a comment without adding another approval. Risk has not increased from the prior documentation-only assessment.

  

_{Sent by Cursor Automation: Assign PR reviewers}