Current documented limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| included Agent usage by planIncluded usage is split into two monthly pools—Cursor models and third-party models charged at provider prices—and on-demand usage continues at API rates once a pool is exhausted. | Pro: extended Agent limits; Pro+: 3× Pro; Ultra: 20× Pro (no dollar amount published) | Individual paid plans (Pro $20, Pro+ $60, Ultra $200 per month) | CursorSep 17, 2026 |
| model context windowSome models bill long context above 272K tokens at 2× input pricing while others keep the same per-token rate; Max Mode extends context only on legacy request-based plans. | Up to 1M tokens with extended or long context on listed models | Usage-based plans; model specific | CursorSep 17, 2026 |
| Max Mode availability and billingCurrent usage-based plans have no Max Mode toggle; they select a context size directly, and a larger context window can increase the tokens a request uses. | Legacy request-based plans only; billed at the model's API rate plus 20% | Legacy request-based plans | CursorSep 17, 2026 |
How to apply Cursor limits safely
The monitored baseline covers included Agent usage by plan, model context window, Max Mode availability and billing. Treat these as separate constraints rather than one platform-wide capacity number: a workload can fit one row and still fail another because the plan, model, endpoint, runtime, region, invocation mode, or account scope differs.
- Match the production workload to the exact scope printed beside each value and confirm it in the active Cursor console, configuration, or response headers.
- Measure the serialized request, token volume, duration, concurrency, storage, or connection demand at realistic percentiles, then preserve headroom for bursts and retries.
- Check every adjacent layer—client, SDK, gateway, proxy, queue, database, and downstream service—for a smaller effective limit before changing architecture.
Specific limit pages
These pages exist because the constraint has a distinct implementation or troubleshooting intent. Closely related keyword variations stay consolidated.
Cursor Included Agent Usage by Plan
Cursor Included Agent Usage by Plan, verified against Cursor's official documentation with scope, implementation impact, caveats, and a direct check.
Cursor Context Window & Max Mode
Cursor Context Window & Max Mode, verified against Cursor's official documentation with scope, implementation impact, caveats, and a direct check.
Cursor Max Mode Usage Limits
Cursor Max Mode Usage Limits, verified against Cursor's official documentation with scope, implementation impact, caveats, and a direct check.