Verified history
This means HyperObserve has not found sufficient first-party evidence for a dated before-and-after event. It does not mean Cursor has never changed. Undated values are kept in the current baseline below instead of being presented as history.
Current monitored baseline
HyperObserve currently monitors 3 scoped observations for Cursor. The baseline covers included API agent usage, model context in Max mode, Max mode consumption. Each value retains its plan, product, endpoint, region, account, or runtime qualifier so a future change can be compared against the correct scope.
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| included API agent usageModel selection and token consumption determine how quickly the included value is used. | Pro $20; Pro+ $70; Ultra $400 in included monthly usage | Individual paid plans | CursorAug 22, 2026 |
| 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 |
| Max mode consumptionInput, cached input, and output use model-specific request-equivalent rates. | Token-priced; draws down included usage faster | Eligible paid plans | CursorAug 22, 2026 |
Tracked constraints and impact
Included agent usage, model context, Max mode, and plan allowances. A change is recorded only when it alters a constraint developers can act on, such as capacity planning, request shaping, model selection, deployment configuration, storage design, retry behavior, or account budgeting.
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.
How a change is verified
- Compare the current first-party statement with the previously stored observation, including the exact plan, model, runtime, endpoint, region, and account scope.
- Separate a true product change from documentation clarification, temporary capacity, configurable account state, or a limit that applies to a different execution path.
- Preserve the old and new values, official source, effective date when disclosed, detection date, and practical impact. If those elements cannot be supported, no historical event is published.
Official sources monitored
These first-party documents support the current Cursor baseline. HyperObserve links directly to them so you can confirm the live wording before making a production decision.
Included agent usage and plan-level allowances
Context windows, Max mode, and request-equivalent costs