Quick answer
Cursor documents model context in max mode as Up to 200K tokens for documented Max-mode models. Normal-mode windows can be smaller and Cursor prunes context as chats grow.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| model context in Max modeNormal-mode windows can be smaller and Cursor prunes context as chats grow. | Up to 200K tokens for documented Max-mode models | Model specific | CursorAug 22, 2026 |
Why does this limit matter?
Attached files, prompts, replies, and tool results compete for the same model conversation budget.
This value is scoped to Model specific; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Confirm the selected model and whether Max mode is active before sizing the task.
- 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
- The active model—not Cursor as a single product—determines the available context and token pricing.
- 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