Cursor pricing: current plans, legacy access and extra usage

Identify the current contract

The checked current monthly offers are Plus USD8, Premium USD30, Super USD100 and Ultra USD200, alongside Free. Legacy Pro and related arrangements remain separately documented. Do not transfer an old Pro allowance to the new Plus offer. First record the effective plan and billed account, then state whether the estimate is for a new purchase or continuation. That small distinction prevents a comparison from combining one contract’s price with another contract’s capacity. The figures are current public offers before applicable taxes, not a promise that an existing account automatically changes to them.

Price the required model route

Plus does not include third-party models and some higher-tier features. On eligible higher tiers, third-party use still has a separate usage charge rather than unlimited inclusion in the subscription. Check the required model and execution surface before multiplying an entry price by headcount. A hypothetical team that mandates a particular third-party model cannot meet that requirement by budgeting Plus seats alone. Establish eligibility first, then estimate volume. A cheaper line is not a usable replacement if it purchases a different model route or excludes the operation the team actually intends to run.

• Choosing Cursor for existing code: editing, review and current plans

Translate the pool into a schedule

Current access uses a weekly pool shared across Cursor and Grok. A monthly average can hide a concentrated release week. Model ordinary weeks separately from a week with a large investigation, then decide whether work may wait or additional usage is permitted. Inspect remaining allowance and the next refresh in the actual account. If other covered features draw from the same subscription, include them rather than assuming every resource is reserved for coding. A larger pool is useful when it resolves a known scheduling interruption, not merely because its printed multiplier is larger.

Hypothetical budget: separate the invoices

For a hypothetical estimate, use the selected subscription plus third-party spending T and other additional consumption U, before applicable taxes. T and U are variables from your measured workload, not official fixed task prices. If ten attempts produce seven accepted changes, allocate all ten attempts across those seven results. Retain human review time in a separate column as well. This makes the economics of a usable patch visible. Longer output should not count as improved value unless it produces work you can actually verify, accept and continue maintaining.

• Cursor vs Claude Code: review surfaces and task handoff

Compare commitment as well as equivalents

Annual access is available, but its monthly equivalent is not a one-month payment arrangement. Use a short pilot to establish required model access and representative work before choosing a longer commitment. For organizations, adding individual prices does not establish the administrative controls you need. Check the actual managed offer and billing conditions. Include possible unused seats and any overlap while migrating from another contract. A discount comparison becomes useful only after those responsibilities are aligned; otherwise the lower apparent monthly amount can conceal a commitment the team has not yet demonstrated it will use.

Verify the end of the old agreement

The current pricing notice says cancellation must occur at least twenty-four hours before renewal to avoid another charge. Verify the applicable agreement and renewal time in the account and avoid depending on a last-minute action. Before changing legacy access, inspect the allowance and model entitlements you would lose. Preserve source, requirements, startup and checks, and have another maintainer continue a patch. Review independent provider agreements separately. Removing an application is not evidence that recurring billing ended; confirm the contractual state where that agreement is actually owned.

• Estimating Claude Code costs: allowance, API usage and accepted changes