Cursor legacy plan: renewal, usage and switching explained
Understand Cursor’s legacy monthly pools, older request-based plans and current weekly usage. Check renewal rules, third-party charges and spending caps.
In this guide
- What does Cursor legacy plan mean?
- Can you keep a legacy Cursor plan at renewal?
- Do monthly pools and weekly usage include the same models?
- Identify the plan from four example account summaries
- Why are there charges above the subscription?
- Why can paid usage pause while credit remains?
- What should you check before switching plans?
- Download the plan check, ledger and review sheet
What does Cursor legacy plan mean?
Cursor uses “legacy” for more than one generation of plan. Its later legacy plans use monthly usage pools; an older arrangement counts requests. Current plans on The X Subscription use weekly included usage. Identify the actual billing model before applying renewal or extra-usage rules.
The legacy-plan documentation, checked on 16 October 2026, separates these generations. A plan name or an old discussion screenshot is not enough to establish an account’s current allowance. Start with the Cursor profile for the product overview.
| Generation | Useful evidence | Question to resolve |
|---|---|---|
| Older request-based | A request allotment and model-specific request counts | What will happen at the next renewal? |
| Legacy usage-based | Cursor Models and Other Models monthly pools | Which pool pays for this request? |
| The X Subscription | Weekly included pool and prepaid additional credit | Is this included usage or a paid request? |
Can you keep a legacy Cursor plan at renewal?
The request-based policy says that older request-based accounts move to usage-based pricing at their next renewal. That is distinct from the optional move to The X Subscription, which is permanent once completed.
Read the actual account notice alongside the matching policy. The broad word “legacy” should not turn those two statements into a promise that request-count terms continue indefinitely, or a claim that every existing account must move to The X Subscription immediately.
Before changing anything, record the account’s plan generation, next renewal, billing channel and proposed destination. If those disagree with a general help page, resolve the account-specific terms first. This article has not opened or changed any subscription.
Do monthly pools and weekly usage include the same models?
The models and pricing overview describes the current paid pool as Cursor-model usage shared across Cursor and Grok. Directly selected third-party models are separate paid usage on eligible tiers. The usage and limits guide describes the legacy arrangement’s two monthly pools and confirms that unused included usage does not roll over. It also distinguishes routing: Cost mode bills as a Cursor-model request; Balance or Intelligence on eligible Teams/Enterprise routes can bill as third-party usage. A named third-party subagent can also have a different billing route from its parent chat.
Compare the actual model and routing choice, not just the number of prompts. An instruction, its code context and the generated response can have different token costs. A larger allowance for one model family does not automatically replace an included allowance for another.
Do not convert weekly availability into an invented monthly dollar budget. Record the displayed next reset date and the required models. The AI coding-agent guide helps define the development workflow before comparing account terms.
Identify the plan from four example account summaries
These are fictional summaries, not screenshots or observations from a real account. Each interpretation uses the supplied billing evidence. D deliberately has insufficient information.
| Case | Supplied labels | Interpretation | Next check |
|---|---|---|---|
| A | Pro; Cursor Models and Other Models; monthly reset | Legacy usage-based plan | Record both pool balances, reset date and on-demand setting. |
| B | Premium; shared weekly pool; prepaid credit | The X Subscription | Separate included Cursor-model usage from paid third-party usage. |
| C | Monthly request allotment; request counts; Max Mode | Older request-based arrangement | Confirm the next renewal notice and destination usage-based plan. |
| D | Ultra only | Insufficient evidence | Read the billing arrangement and usage meters; the name exists in both families. |
“Ultra” appears in both the legacy and current families. Confirm the account or workspace being billed and read its usage meters before choosing documentation. Keep personal and employer-provided accounts separate in the review.
Why are there charges above the subscription?
The additional-usage guide distinguishes prepaid top-ups on The X Subscription from legacy on-demand usage billed later. For later legacy individual Pro, Pro+ and Ultra plans, on-demand usage requires enabling; legacy Teams has a different default. Check the actual arrangement rather than transferring an individual-account assumption to a team.
Buying credit, consuming credit and paying the base subscription are separate events. Auto Top-up can create another payment when its threshold is met. Turning it off does not erase credit already held or prevent that balance from being consumed.
Use the invoice, usage entry and credit transaction for the same account and period. A subscription receipt alone cannot explain all additional charges. The worksheet leaves actual charges and evidence blank until you inspect them.
Why can paid usage pause while credit remains?
The spending-cap guide says the current monthly additional-usage limit counts paid consumption, not credit purchases. Buying more credit does not raise that cap. Included weekly usage and the paid-consumption cap therefore need separate checks.
This idealised USD ledger starts with $50.00 already held and an assumed $15.00 cap. The amounts and credit purchase are invented, not a published top-up package, model price or actual account bill. All five steps occur within the same cap period; no credit expires.
| Step / event | Credit bought | Paid use in this step | Credit remaining | Used toward cap | Cap room |
|---|---|---|---|---|---|
| 1 / Opening balance | $0.00 | $0.00 | $50.00 | $0.00 | $15.00 |
| 2 / Consume paid additional usage | $0.00 | $12.00 | $38.00 | $12.00 | $3.00 |
| 3 / Purchase additional credit | $10.00 | $0.00 | $48.00 | $12.00 | $3.00 |
| 4 / Consume the remaining cap room | $0.00 | $3.00 | $45.00 | $15.00 | $0.00 |
| 5 / Included weekly pool resets | $0.00 | $0.00 | $45.00 | $15.00 | $0.00 |
After the assumed purchase, credit rises to $48 while cap room stays $3. Spending that $3 leaves $45 of credit and no cap room. A weekly included-pool reset does not reset this monthly cap. Eligible included usage may still work; paid additional usage can remain paused.
Across the example, $10 of new credit is bought and $15 is consumed from the balance. Adding those as a $25 usage bill would double count different measures. The subscription, earlier credit purchases, tax and complete invoice amount are not modelled. Real limit enforcement can lag; this clean ledger is not a guarantee of an exact instantaneous stop.
What should you check before switching plans?
Write down the development work the account must support, the models it uses, the current allowance and reset dates, and the evidence behind any extra charges. Then compare the proposed subscription, paid usage, cap and feature scope on the same basis.
The reviewed switching page says the move to The X Subscription cannot be undone by Support. Its Apple-billed Cursor exception also requires separate attention to the old App Store subscription. Read the actual channel-specific instructions before authorising a switch; merely checking a price or this worksheet does not change an account.
For a broader shortlist, use GitHub Copilot versus Cursor. Record accepted code, tests and handover requirements as well as billed usage. A cheaper-looking base price is insufficient evidence of lower total development cost.
Download the plan check, ledger and review sheet
Download the four plan cases ↓
Download the five-step credit ledger ↓
Download the six-question account review ↓
Read the scope and assumptions ↓
Replace the examples with evidence from the authorised account. Actual plan, renewal, observed result, invoice evidence and decision fields remain blank. These files do not connect to Cursor, estimate token costs, set limits, buy credit or switch subscriptions.
Frequently asked questions
What is a Cursor legacy plan?
The term covers later legacy plans with monthly usage pools and an older request-count arrangement. Current plans on The X Subscription use weekly included usage. Identify the actual generation before applying its rules.
Can I keep my Cursor legacy plan at renewal?
The older request-based policy describes migration to usage-based pricing at renewal. The later legacy usage-based documentation describes the move to The X Subscription as optional. Check the actual account notice and billing model; these are different transitions.
Does every Cursor legacy plan include 500 requests?
No universal 500-request allowance follows from the word legacy. Later legacy plans use monthly usage pools. Older request-based terms and model request counts need their own account-specific check.
Are third-party models included in the current weekly pool?
Directly selected third-party models on eligible Premium-and-above plans draw on prepaid credit. Auto Cost is a separate billing route documented as a Cursor-model request; eligible team Balance/Intelligence routes follow the selected provider. Check request-level usage, not just the parent chat label.
Does Cursor Auto always bill from the same usage pool?
The reviewed usage guide distinguishes Cost from team Balance/Intelligence routing. Named third-party subagents can also use a different pool or paid route from their parent. Inspect the actual request and account generation.
Does buying more Cursor credit raise my spending cap?
The current monthly additional-usage cap counts paid consumption. Purchasing credit adds balance without raising that cap; paid usage can pause with credit still available.
Does the weekly usage reset clear the monthly spending limit?
They measure different periods and populations. The worked example stays inside one monthly cap period, so the weekly included-pool reset leaves its paid-consumption cap room unchanged.
Can Support undo a switch to The X Subscription?
The reviewed switching documentation says the move is permanent and Support cannot reverse it. Confirm the actual account, billing channel, usage and feature implications before changing plans.
Does the Cursor Ultra name tell me which billing model I have?
No. Ultra appears in both later legacy and current plan families. Read the billing arrangement, usage meters and account or workspace being charged.
Put the guide into practice
Explore ai coding assistants tools, then compare your shortlist.
Explore the category →