How do Cursor usage limits work?
Cursor paid plans currently track two monthly pools: Cursor Models for Cursor Grok 4.5 and Composer 2.5, and Other Models for third-party models. Pro, Pro Plus and Ultra currently include $20, $70 and $400 of Other Models usage respectively, plus a separately tracked Cursor Models allowance. Auto can draw from either pool according to the routed model and mode. Both reset with the billing cycle; unused included usage does not roll over. Verified 2026-08-08.
How Cursor's two usage pools work
| Pool or route | Current coverage | How usage is counted |
|---|---|---|
| Cursor Models | Cursor Grok 4.5 and Composer 2.5 | Separate included pool shown in the Spending tab |
| Other Models | Third-party models | Model-provider rates consume the plan's included allowance |
| Auto Cost | Router-selected model | Bundled Auto pricing |
| Auto Balance / Intelligence | Router-selected model | Routed model rate; can draw from either pool |
Why — the first-principles explanation
A Cursor subscription does not provide one undifferentiated bucket of requests. It provides two separately measured pools. The Cursor Models pool currently covers Cursor Grok 4.5 and Composer 2.5. The Other Models pool covers third-party models and consumes allowance according to the applicable model-provider rate.
The current individual plan summary lists $20 of Other Models usage on Pro, $70 on Pro Plus and $400 on Ultra, alongside separately tracked Cursor Models usage. Those figures are included usage, not guaranteed total monthly charges: on-demand usage can add charges only when it has been explicitly enabled.
Auto does not belong permanently to one pool. Cursor Router selects a model per request. Auto Cost keeps bundled Auto pricing. Balance and Intelligence bill at the routed model's rate and can draw from either pool depending on which model handled the request. That is why an Auto-heavy workflow cannot be estimated accurately by labeling Auto itself "first-party."
Both pools reset with the applicable monthly billing cycle, and unused included usage does not roll over. The Spending tab is the authoritative account view: it shows each pool, remaining allowance, the reset date and any on-demand line items.
An example that makes it click
Picture two transit cards in the same wallet. Cursor Models has one balance; Other Models has another. Choosing a named model tells you which card is likely to be tapped. Auto is the gate attendant: Cost uses a bundled fare, while Balance or Intelligence can tap either card based on the model routed for that trip. The Spending tab is the receipt showing what actually happened.
How to do it
- Check your current usage in Cursor under Settings > Usage or your account dashboard.
- Read the Cursor Models and Other Models balances separately in the Spending tab.
- Use the model picker to distinguish named Cursor Models from named third-party models.
- For Auto, note whether you selected Cost, Balance or Intelligence; the modes do not share one billing rule.
- Keep on-demand usage disabled if you want requests to stop rather than create on-demand usage after included usage runs out.
- If you enable on-demand usage, set a correctly scoped spend limit and monitor the separate on-demand line items.
- Use the reset date shown in the account dashboard; both included pools reset with the billing cycle and do not roll over.
Key facts
- Current included Other Models usage: Pro $20, Pro Plus $70 and Ultra $400, with a separately tracked Cursor Models pool.
- The Cursor Models pool currently includes Cursor Grok 4.5 and Composer 2.5; Auto is routing rather than a fixed model in that pool.
- Other Models usage is charged against allowance at the applicable model-provider rate.
- Auto Cost uses bundled pricing; Auto Balance and Intelligence use routed-model rates and can draw from either pool.
- Both pools reset with the monthly billing cycle, and unused included usage does not roll over.
- On-demand usage must be explicitly enabled and appears separately from included usage.
Open the current official limits, credits and plan rules before relying on the allowance.
Use the right guide for models, outcomes and cost controls
This page explains the pool mechanics. The related guides cover model selection, what happens at a limit and how to configure a cap.
▶ The 60-second explainer (script)
How do Cursor's usage limits work? Simple idea: every AI request costs Cursor real money, so instead of truly unlimited access, you get a monthly budget. There are actually two pools. First, a dollar budget for premium third-party models, about twenty dollars on Pro, seventy on Pro Plus, and four hundred on Ultra. Second, a separate, much more generous pool for Cursor's own models, Auto, Composer, and Grok, which are cheaper for them to run. Here's the key: the model you pick decides how fast you burn through the budget. Expensive frontier models on huge files drain it quickly; using Auto or Composer for everyday work barely dents it. Your limits reset on your billing date each month, and unused usage does not roll over. When you get close, Cursor shows a notification, and you can either enable pay-as-you-go billing or upgrade. Choose your models wisely and the budget goes a long way.
What authoritative sources say
People also ask
Do Cursor limits reset each month?
Yes, on your subscription billing date. Unused usage does not carry over to the next month.
Why does my usage disappear so fast?
Model rate, routed Auto mode and context size all matter. Check request-level details in the Spending tab instead of assuming Auto or a named model always uses the same pool.
What's the difference between the two usage pools?
Cursor Models currently covers Cursor Grok 4.5 and Composer 2.5. Other Models covers third-party models. They are tracked separately in the Spending tab.
Can I buy more usage?
Yes. Enable usage-based (pay-as-you-go) billing or upgrade to a higher plan for a bigger monthly budget.