Guide
Pin, Watch, or Cancel: What Cursor's List-Price Auto Means for a $20 Pro User
Cursor now documents list-price billing for Auto, but its new Router modes are not yet on individual plans. A framework for pinning models, watching usage, or leaving.
If you use individual Cursor Pro at $20 a month, do not assume every Auto announcement or Router control applies to your account today. Cursor’s current documentation says Auto requests bill at the list price of the model selected, but it also says the new Cursor Router is currently available only on Teams and Enterprise; individual plans will receive that update later.
If your question is instead what happens when a contractor leaves a paid team, use the separate Cursor Teams seat-removal guide. It distinguishes Teams’ occupied-seat and future-invoice-credit language from the individual 14-day unused-payment review; this article does not cover that lifecycle.
That split changes the decision:
- Pin a model if a named, lower-cost model already ships your work.
- Watch usage if Auto saves enough time and the two included pools survive a normal billing cycle.
- Cancel or switch if on-demand charges are recurring or the account does not give you enough cost visibility to quote client work.
Rates and product rules below were checked on 28 August 2026. Cursor changes model pools and pricing, so confirm current details in the model picker, pricing reference, and Spending dashboard.
What is confirmed, and what is still rollout-dependent
An r/cursor post from 19 August transcribes an email saying a pricing change would take effect on 24 August 2026. The transcribed text says Auto pricing would follow the model each request is routed to instead of a flat rate, and that “for most requests” the rate would be higher. It also says included usage for Cursor Models, including Auto, would increase in the current billing cycle and that routing behavior would not change.
That post is evidence of a user-reported email, not a public Cursor announcement or proof that every individual Pro account received the same rollout on the same date. The current official docs provide the durable facts:
- Pricing and plans lists individual Pro at $20 per month, Pro+ at $60, and Ultra at $200.
- The same page says all Auto modes bill at the list price of the routed model.
- It also says Cursor Router launched for Teams and Enterprise, while Hobby, Pro, Pro+, and Ultra will receive the update a few months later.
- Cursor Router docs say the three modes are Cost, Balance, and Intelligence and that Router is currently only available on Teams and Enterprise.
For an individual Pro user, the safe instruction is therefore: check the model picker and billing dashboard. Do not follow a Teams-only mode tutorial until those controls exist on your account.
The two usage pools and the verified rate card
Cursor’s usage and limits page describes two monthly pools:
- Cursor Models: Cursor Grok 4.6, Cursor Grok 4.5, and Composer 2.5.
- Other Models: third-party models charged at provider prices.
Pro, Pro+, and Ultra include both. Usage resets with the monthly billing cycle, unused usage does not roll over, and the public table labels both pools “Included” without publishing their dollar size. The Spending dashboard is the account-specific source for real-time usage, remaining allowance, reset date, and on-demand charges.
The Models & Pricing table listed these prices per million tokens on 28 August:
| Model | Input | Cache read | Output |
|---|---|---|---|
| Composer 2.5 | $0.50 | $0.20 | $2.50 |
| Composer 2.5 (Fast) | $3 | $0.50 | $15 |
| Cursor Grok 4.6 | $2 | $0.50 | $6 |
| Cursor Grok 4.6 (Fast) | $4 | $1 | $12 |
| Cursor Grok 4.5 | $2 | $0.50 | $6 |
| Cursor Grok 4.5 (Fast) | $4 | $1 | $18 |
| GPT-5.6 Luna | $0.20 | $0.02 | $1.20 |
| Claude Opus 5 | $5 | $0.50 | $25 |
| Claude Fable 5 | $10 | $1 | $50 |
Luna, Opus, and Fable also have cache-write rates on the source table. They are omitted here because the worked example below assumes no cache hits or writes.
Teams and Enterprise need one additional line: third-party Router requests also incur Cursor’s $0.25 per million token Cursor Token Rate. Composer 2.5 carries no such surcharge. That surcharge does not apply to an individual Pro seat in this article’s example.
The old flat rate is only an Enterprise comparator
Cursor’s Router page says that until 7 September 2026, Enterprise Auto Cost pricing is fixed at $1.25 input, $1.25 cache write, $0.25 cache read, and $6 output per million tokens regardless of model.
Those figures are not a current individual Pro entitlement. They can be used as a labeled historical comparator, but not as a promise about a Pro invoice or as proof of the old individual Auto rate.
Worked example (assumptions labeled)
This prices modeled token usage, not your bill. Included pool sizes are not public, so the results cannot tell you when a Pro account will run out.
Assumptions:
- Individual Cursor Pro at $20 per month.
- One client sprint with 20 agent-heavy hours.
- Per agent-hour: 2 million input tokens and 0.4 million output tokens.
- No cache hits, cache writes, regional uplift, or Team/Enterprise Token Rate.
Cost per modeled agent-hour is 2 × input rate + 0.4 × output rate.
| Route used for the model | Modeled cost per hour | Modeled value for 20 hours |
|---|---|---|
| Composer 2.5 | $2.00 | $40 |
| Cursor Grok 4.6 | $6.40 | $128 |
| Enterprise flat-rate comparator | $4.90 | $98 |
| Claude Opus 5 | $20.00 | $400 |
| Claude Fable 5 | $40.00 | $800 |
The arithmetic shows the width of the list-price band. Under these assumptions, Composer is about 2.45x cheaper than the Enterprise comparator, Grok 4.6 is about 31% more expensive, and Fable is about 8.16x the comparator.
Do not interpret $40, $128, or $800 as an invoice. Included usage absorbs some or all modeled value until a pool is exhausted, and on-demand charges apply only when on-demand is enabled. The public docs do not disclose the pool sizes.
Cursor’s own usage guide says daily Tab users typically stay within included usage, limited Agent users often do, daily Agent users commonly represent $60–$100 per month in total usage, and power users often represent $200 or more. “Total usage” is usage value before included allowances, not necessarily the amount charged to a card.
Pin, watch, or cancel
Pin a named model when repeatable work already passes review on Composer 2.5, Cursor Grok, or another affordable model. A pinned model makes the rate visible before the request. It also lets an individual Pro user act now without pretending that Teams-only Balance or Intelligence controls are available.
Watch and renew when Auto materially improves delivery. Record the two pool balances, reset date, request-level cost and pool details, and on-demand charges once a week. Router’s underlying model is hidden by default on Teams and Enterprise unless an administrator changes that policy, so record the routed model only when the interface actually displays it. Judge renewal on invoice plus labor saved, not the $20 headline or the $60–$100 usage-value range alone.
Cancel or switch when on-demand is needed in most cycles, when cost cannot be estimated before client work, or when a pinned model in another editor produces the same accepted output. Cancellation is not a claim that Router quality is poor; it is a decision that the metering or visibility does not fit the job.
Upgrading to Pro+ or Ultra buys more included usage, but it does not remove the need to identify which pool the work consumes. Move up only after a full Pro cycle shows that the larger allowance is cheaper than recurring on-demand spend and the value of time saved.
Decision checklist
- Open the Spending dashboard and record both pools, the reset date, and on-demand charges.
- Confirm whether your individual account still has the old Auto experience or has received the new Router controls.
- Price one representative sprint with the named models you would pin.
- Renew if measured labor savings exceed subscription plus on-demand cost; switch if recurring spend or uncertainty breaks the client budget.
Sources checked 28 August 2026: Models & Pricing, Pricing and plans, Usage and limits, Cursor Router, and the user-posted email transcription.