What happens when you hit Cursor usage limits?
First identify which limit you hit. If an included usage pool runs out, Cursor shows an editor notification; requests stop unless on-demand usage is enabled, in which case eligible requests can create on-demand charges. If a configured spend limit is reached, AI features stop for the limit's user, team or Enterprise scope until the next billing cycle or an authorized limit change. Usage resets with the billing cycle. Verified 2026-08-08.
What happens at each Cursor limit
| Limit reached | On-demand usage | Immediate result | Next choices |
|---|---|---|---|
| Included pool | Off | Requests using that exhausted allowance stop | Use an available other pool, upgrade or wait for reset |
| Included pool | On | Eligible requests continue as on-demand usage | Monitor charges or set a spend cap |
| Spend limit | Already capped | AI features stop for the configured scope | Authorized change or next billing-cycle reset |
Why — the first-principles explanation
Cursor uses the word limit for at least two different boundaries. An included usage limit is the allowance bundled with a plan. A spend limit is a cap you or an administrator configured for on-demand usage. The result depends on which boundary was reached.
When included usage runs out, Cursor documents an editor notification. If on-demand usage is disabled, requests stop instead of creating new on-demand charges. If it is enabled, eligible requests can continue and are recorded as on-demand usage under the current pricing rules. On-demand usage must be explicitly enabled; reaching an included allowance does not by itself authorize an extra charge.
Cursor also tracks Cursor Models and Other Models as separate pools. Exhausting one pool does not prove the other is empty. Composer 2.5 and Cursor Grok 4.5 currently use the Cursor Models pool, while third-party models use Other Models. Auto routing can draw from either pool depending on the routed model and mode.
A spend cap is different. When it is reached, AI features stop for the applicable scope. An individual or member cap affects that user; a Teams team-level cap can affect all members consuming on-demand usage; Enterprise can use team, group, member and pooled controls. Check the label and scope in the Spending tab before changing anything.
An example that makes it click
Think of two prepaid balances plus a circuit breaker. Cursor Models and Other Models are separate balances. On-demand usage is permission to keep buying after an included balance is empty. A spend limit is the circuit breaker that cuts off that paid continuation at the chosen user or team scope. Seeing "limit reached" tells you a boundary was crossed; the Spending tab tells you which one.
How to do it
- Read the editor notification, then open cursor.com/dashboard/spending to identify the exhausted pool or spend cap.
- Check Cursor Models and Other Models separately; do not assume both are exhausted.
- If you do not want on-demand model-usage charges, leave on-demand usage off and wait, change model pool if appropriate, or upgrade deliberately.
- If you enable on-demand usage, set a spend limit for the correct individual, team or Enterprise scope and monitor the on-demand line items.
- For Auto, check whether Cost, Balance or Intelligence handled the request because routing and pricing behavior differ.
- Use the reset date displayed in the Spending tab rather than guessing from a calendar date.
Key facts
- Cursor shows an in-editor notification when included usage is exhausted.
- On-demand usage must be explicitly enabled; otherwise requests stop instead of creating on-demand usage charges.
- Cursor Models and Other Models are separate pools, and Auto can draw from either depending on the routed model.
- A spend limit stops AI features for its configured user, team or Enterprise scope when reached.
- Usage resets monthly with the applicable billing cycle and unused included usage does not roll over.
- Teams and Enterprise third-party-model requests may include Cursor Token Rate; individual and business billing terms are not interchangeable.
Open the current official limits, credits and plan rules before relying on the allowance.
Choose the right next action for the limit you hit
The model pool, on-demand switch and spend-limit scope are separate controls. Use the guide that matches the change you intend to make.
▶ The 60-second explainer (script)
What happens when you hit your Cursor usage limit? Don't worry, nothing breaks. Cursor shows a notification right in the editor telling you you've used up your budget. This is a billing guardrail, since every premium AI request costs real money, Cursor stops before you overspend. Then it hands you the choice. Option one: enable usage-based billing to pay as you go and keep using premium models. Option two: upgrade to a bigger plan like Pro Plus or Ultra. Option three, and this one's free: switch your model to Cursor's own Auto or Composer. Those pull from a separate, generous pool that's usually not exhausted, so you can often keep working for free until your reset. And option four: just wait. Your budget refills automatically on your monthly billing date, though unused amounts don't roll over. So hitting the limit isn't a dead end, it's a menu of ways to keep going.
What authoritative sources say
People also ask
Does Cursor charge me automatically when I hit the limit?
Not merely because an included allowance was reached. On-demand usage must already be explicitly enabled for eligible requests to continue as on-demand usage.
Can another model still work after one pool is empty?
Possibly. Cursor Models and Other Models are tracked separately, but check the Spending tab rather than assuming another pool has remaining allowance. Auto is routing, not a guaranteed free fallback.
When does my usage reset?
On your monthly subscription billing date. Unused usage does not carry over.
How do I avoid unexpected on-demand usage charges?
Keep on-demand usage disabled for a hard stop, or enable it deliberately and set a spend limit for the correct user or team scope. A spend alert only notifies; it does not cap usage.