Updated August 29, 2026: Cursor pricing is no longer just a monthly subscription question. The plan you choose controls how much model usage is included, which usage pool a request consumes, and whether additional usage can be billed after the allowance runs out.
Our verdict: Cursor is good value for developers who use its editor, agent workflow and model choice every week, but the headline subscription price can hide the real variable: model consumption. Pro is a sensible entry point. Pro+ is aimed at regular agent users, while Ultra is for heavy users who can justify a much larger fixed monthly commitment. If you want a hard ceiling, disable on-demand usage or set a spend limit before handing an agent a large repository.
This is a current explainer, not a defence of the old headline “Cursor’s New Pricing Is a Disaster.” Cursor itself acknowledged in 2025 that the pricing rollout and communication were confusing. The useful question in 2026 is simpler: how much does your completed coding work cost, and can you control the upper bound?
Cursor pricing at a glance
Cursor’s current pricing documentation lists the following monthly plans. The India-only Start price is tax inclusive; other listed prices may have applicable taxes. Annual billing, regional checkout and promotions can change the amount shown at payment.
| Plan | Listed price | Best fit | Important usage note |
|---|---|---|---|
| Hobby | Free | Trying the editor and occasional AI assistance | Limited Agent requests; Composer access |
| Start (India only) | ₹649/month, tax inclusive | India-based users who need a lower-cost local plan | Cursor Models pool only, according to Cursor’s usage guide |
| Pro | $20/month | Individual developers and daily Tab/limited Agent users | Includes both usage pools; Cursor documents $20 of API agent usage plus bonus capacity |
| Pro+ | $60/month | Daily Agent users who regularly need more included usage | Cursor documents $70 of API agent usage plus bonus capacity |
| Ultra | $200/month | Power users running agents, automation or large workloads | Cursor documents $400 of API agent usage plus bonus capacity |
| Teams Standard | $40/user/month | Teams needing administration and shared controls | Centralized billing, analytics, privacy mode and SSO |
| Teams Premium | $120/user/month | Teams needing a higher Agent allowance | Five times Standard Agent limits, according to the plan table |
| Enterprise | Custom | Organizations needing pooled usage and governance | SCIM, audit logs, access controls, invoicing and priority support |
Sources: Cursor’s pricing and plans documentation, Cursor Models & Pricing and the official pricing page. Check the destination pages because Cursor can change plan names, limits and regional availability without preserving an old comparison.
Why the subscription price is not the whole bill
Cursor separates the subscription from the model work performed inside it. Its current usage guide describes two monthly pools on most paid plans:
- Cursor Models: first-party options such as Grok 4.6, Grok 4.5 and Composer 2.5.
- Other Models: third-party models whose consumption is tied to the provider’s API pricing.
Model selection changes how quickly included usage is consumed. A long, tool-heavy task using a high-cost model can draw down an allowance much faster than a short edit. That is why “I have a $20 plan” does not mean every model request has the same effective price or count.
Cursor’s Models & Pricing page currently describes guaranteed API agent usage of $20 for Pro, $70 for Pro+ and $400 for Ultra, with additional bonus capacity that Cursor says it tries to provide. Treat the guaranteed amount as the planning number and bonus capacity as a possible extra—not as a contractual quota.
What happens after you hit the included limit?
If on-demand usage is enabled, Cursor says extra requests are billed in arrears at API rates with no markup. The dashboard separates included usage from on-demand usage. If on-demand usage is disabled, requests stop when the included allowance is exhausted rather than silently converting into a larger invoice.
The official overage guide also warns that enforcement is not instant: usage can briefly exceed a spend limit before the system recognizes the threshold. Cursor says that limited excess is handled as a temporary spend-limit credit and that raising the limit in the same billing cycle can make some or all of it billable. A limit is a useful guardrail, not a millisecond-perfect circuit breaker.
Worked cost examples
These examples are deliberately simple. They show the budgeting logic, not a promise of what any particular model request costs.
Light use: Pro is enough
Assume a developer completes 40 small tasks in a month and the dashboard reports $0.20 of model usage per task. The usage total is 40 × $0.20 = $8. The monthly Pro subscription remains $20, so the pre-tax total is $20 and no on-demand usage is required. The key variable is the dashboard-reported usage, not the number of prompts alone.
Regular use: Pro plus controlled overage
Assume 100 tasks average $0.30 each. That is $30 of model usage. If the account has the Pro plan’s $20 included API usage and on-demand is enabled, the illustrative excess is $10. The subscription plus usage becomes $30 before taxes and any model-specific details. If the developer cannot accept that uncertainty, the safer setting is to disable on-demand and allow the editor to stop at the included limit.
Heavy use: compare Pro+ with Ultra using real logs
Assume a team’s monthly dashboard shows $140 of frontier-model consumption before bonus usage. Pro+ has a $60 subscription and a documented $70 API-usage allowance; Ultra has a $200 subscription and a documented $400 allowance. The right decision depends on the actual mix of models, the value of time saved, and whether the team needs Ultra’s headroom. Do not multiply a “20×” marketing comparison into $4,000 of guaranteed credit: Cursor’s current documentation lists $400 for Ultra’s API agent usage, with bonus capacity handled separately.
How to avoid surprise bills in Cursor
- Open Cursor’s dashboard and inspect Included Usage and On-Demand Usage before starting a large task.
- Turn off on-demand usage if a hard stop matters more than uninterrupted work.
- If on-demand is necessary, set a spend limit and leave it unchanged after the limit is reached unless you intentionally accept more billing.
- Use a cheaper or first-party model for routine edits and reserve premium models for tasks where their quality changes the outcome.
- Keep prompts, repository selection and tool permissions narrow. An agent that repeatedly scans a huge workspace can consume more than a focused request.
- Record the model, task type, tokens, retries, latency and completed outcome. A cheaper request that fails twice is not necessarily cheaper.
- For teams, use usage analytics, model allow/block lists and privacy settings to make the policy visible to every seat.
Is Cursor pricing actually a disaster?
Our analysis is more specific: Cursor’s pricing is understandable once it is treated as a hybrid subscription-plus-usage system, but it is easy to misunderstand if the plan card is read as an unlimited pass to every frontier model. The 2025 backlash was partly a communication failure. The 2026 risk is operational: a developer can confuse a generous plan with an uncapped budget, or compare Cursor’s subscription with another tool’s subscription while ignoring different model and token accounting.
The best metric is cost per completed, accepted task. Track how many requests, retries and tool calls produce a merged change, then compare that workflow with alternatives such as a hosted API, GitHub Copilot or a local model. For a broader discussion of why model routing and efficient inference matter, see Eyestech’s analysis of the flash-model economics.
Who should choose which plan?
- Curious or occasional users: start with Hobby and learn how Agent and Composer consume usage.
- Individual developers: Pro is the sensible baseline when Cursor is part of the daily editor workflow.
- Daily Agent users: Pro+ is easier to justify when the dashboard repeatedly shows that Pro’s allowance is too small.
- Power users: Ultra can make sense when the time saved and predictable included capacity are worth the fixed commitment.
- Teams: choose Teams or Enterprise for administration, privacy, analytics and governance—not merely for a larger personal quota.
Bottom line
Cursor’s current plans range from free Hobby to $200/month Ultra, with an India-only ₹649 Start plan and team tiers up to custom Enterprise. The subscription gives access to a usage system; it does not erase model economics. Check the official pricing and usage pages on the day you subscribe, inspect the Spending dashboard, and decide deliberately whether on-demand usage is acceptable.
Editorial note: This article is an independent Eyestech analysis. Prices and model availability were checked on August 29, 2026, and may change. Cursor is a trademark of Anysphere, Inc.; Eyestech is not affiliated with Cursor.
