Cursor Spent Its Goodwill on a Pricing Change and Is Still Rebuilding
Cursor’s technical reputation was earned quickly and its commercial reputation was damaged almost as fast. In June 2025 the company moved Pro subscribers from a request-counted model to one billed against actual token consumption, and did so without adequately explaining what the word unlimited had come to mean. Its own follow-up post concedes the failure, offers refunds for a specific window, and sets out the replacement structure. A year on, the editor is still among the best available and the billing still rewards attention.
What actually happened in June 2025
Under the previous arrangement, Pro included 500 requests a month, with Sonnet-class models counting as two requests each. From 16 June 2025 that was replaced by usage measured at API pricing. The company’s public explanation acknowledges that it marketed unlimited usage while that guarantee in fact applied only to Auto mode, not to frontier models, and that the ambiguity produced charges users had not anticipated.
Cursor committed to refunding unexpected charges incurred between 16 June and 4 July 2025 and directed affected customers to a dedicated address. It also promised clearer documentation and dashboard visibility as usage approaches a limit. Taken together the post is a reasonably candid apology, which is more than most vendors manage, and it does not undo the fact that people were billed for something they believed was included.
The episode matters beyond Cursor. It was the clearest early example of a pattern that has since spread across AI tooling: a subscription price that functions as a credit float against variable model costs, wearing the clothes of a flat monthly fee.
It is also worth being fair about the underlying economics. Frontier model inference genuinely costs money, and a flat 20 dollar subscription cannot fund unbounded use of the most capable models available. Every serious competitor has arrived at some version of the same conclusion. What distinguishes the Cursor episode is not that the company introduced a meter but that it did so while the previous language still implied there was not one.
Twenty dollars buys twenty dollars of model usage
The current Pro plan is $20 a month and includes unlimited Tab completions and unlimited Auto-model usage, plus $20 of frontier model consumption charged at API rates. Cursor’s own illustration puts that allowance at roughly 225 Sonnet 4 requests, or around 550 Gemini or 650 GPT-4.1 requests, depending on context size.
The honest reading is that Pro is a pass-through with a floor. Heavy agentic work on a large codebase consumes context aggressively, and a developer running long multi-file refactors will exhaust the allowance well before month end. Light users subsidise nothing and heavy users pay in arrears, which is economically rational and psychologically uncomfortable for anyone accustomed to fixed software costs.
The unlimited Auto mode is the release valve, and it is a real one. Auto routes to whichever model Cursor considers appropriate and capable at that moment, and for routine work it is frequently good enough. Developers who discipline themselves to reserve frontier models for genuinely hard problems can stay inside the allowance indefinitely.
Pro+, Ultra and the team tiers
Above Pro sit Pro+ and Ultra, described on the pricing page as offering three times and twenty times the Pro agent limits respectively, along with higher Grok usage ceilings and priority access to new features. The page does not display prices for either tier, which is a curious omission given the history.
For teams, Standard is $40 per user per month and brings centralised billing and administration, shared-context cloud agents, agentic code review, usage analytics and SAML or OIDC single sign-on. Premium is listed at five times the Standard agent limits, again without a published figure.
The usage analytics on the team plans are more important than they sound. Given that individual consumption varies by an order of magnitude between developers, an engineering manager buying Cursor without per-seat visibility is signing a blank cheque. That the analytics only appear at $40 a seat is a defensible commercial decision and an awkward one for small teams.
The absence of published prices for Pro+, Ultra and Teams Premium is the part that sits least comfortably given what happened in 2025. A company that damaged its standing through pricing opacity has responded by leaving three of its six tiers unpriced on the page that exists to communicate price. Prospective buyers can find the figures readily enough in secondary coverage, which rather undermines any argument that the omission serves a commercial purpose.
What the editor does that justifies any of this
None of this is replicated cheaply. The competition has narrowed the gap considerably since 2025, but Cursor’s editing experience is still the reference point, and for a professional developer the productivity argument overwhelms a 20 dollar subscription. The argument that does not survive scrutiny is the one about predictable cost. Budget for the plan and then budget again for the usage, monitor consumption from the first week, and treat any month without an overage as a pleasant surprise rather than the expected outcome.
One last practical note for anyone evaluating now. Because the allowance is denominated in dollars of model usage rather than in requests, the effective value of a Cursor subscription moves whenever the underlying model prices move, in either direction. That has generally favoured subscribers as inference costs have fallen, but it also means the plan you are comparing today is not a fixed quantity, and any internal business case built on a request count will be wrong within a quarter.
- Tab completion that predicts multi-line edits rather than single tokens, which remains its strongest feature
- Codebase-wide context retrieval that answers questions about unfamiliar repositories quickly
- Agent mode that executes multi-file changes and runs tests, with review before acceptance
- Support for rules files, hooks and MCP servers, allowing project-specific conventions to be enforced
- A VS Code lineage, so existing extensions, keybindings and settings largely carry across
Sources: Cursor blog, clarifying our pricing · Cursor pricing · Vantage, Cursor pricing explained · Tessl, Cursor’s new pricing structure explained
