Quick answer
Cursor documents max mode availability and billing as Legacy request-based plans only; billed at the model's API rate plus 20%. Current 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.
Verified Sep 17, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| 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 |
Why does this limit matter?
A team that migrated to usage-based pricing cannot rely on Max Mode, and on a legacy plan a Max Mode task costs the model's API rate plus 20%.
This value is scoped to Legacy request-based plans; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Open Cursor's billing settings to see whether the account is still on a legacy request-based plan before planning around Max Mode.
- Confirm the exact plan, model, runtime, endpoint, region, and account that serve the failing workload.
- Record the observed value, response headers or configuration, timestamp, and source without logging secrets.
Important caveats
- Legacy request-based plans are migrated to usage-based pricing at renewal, after which Max Mode is no longer offered.
- Treat the official source and live account configuration as authoritative if they differ from this verified snapshot.
HyperObserve reports the documented platform constraint. Your application, SDK, gateway, provider, region, or account can impose a lower effective limit.
Related