The Cursor pricing crisis of June 2025: what happened, what users did, what it means

In mid-June 2025 Cursor changed how its Pro plan works. The old plan — $20/month for 500 fast requests + slow-mode fallback — became $20/month for “$20 worth of usage at API rates,” with no explicit unlimited tier. For users who had been on the old “unlimited slow” tier, the change felt like a unilateral price hike of several times. The community reaction is among the loudest backlashes any AI-coding tool has faced.

This piece is the working engineer’s read on what actually happened, what users did about it, and what the rest of 2025 looks like for the AI IDE market.

The timeline

June 16, 2025: Cursor publishes a blog post describing the new pricing model. Pro is still $20/month but now “buys $20 of usage at API rates.”

Within 48 hours: Heavy Cursor users on the old plan start hitting limits they had never seen. The viral r/cursor thread “Cursor is unusable now — $20 = 6 hours of usage” hits 450 upvotes. The top reply: “Nothing compares to CC at this point. I can’t think of a single product that has deteriorated so quickly in terms of stability and value.”

End of June: Multiple “I switched to Claude Code” threads dominate r/cursor. A surprising amount of “I switched BACK to VS Code + Copilot” — see Cursor’s price is wild, I jumped back to VS Code (204 ups).

July 4, 2025: Cursor publishes an apology, reported by TechCrunch. Refunds offered for unexpected charges between mid-June and early July. New “more transparent” tiers announced.

August–September: Cursor iterates pricing tiers multiple times. The community signal stabilises but trust is meaningfully eroded; “Cursor is what I use until I find time to migrate” becomes a recurring sentiment.

What actually broke

Three things mattered, in roughly decreasing order:

1. The communication. The blog post used language that obscured how much heavy users were going to pay. The old “500 fast / unlimited slow” formula was simple to reason about. The new “$20 of usage at API rates” is technically more honest but the implication — that heavy users would burn through their $20 in days — was not clearly communicated.

2. The math. For light Cursor users, the new pricing is barely different. For users running Claude Opus or GPT-4o heavily, the new pricing is several times more expensive than the old “unlimited slow” tier. Heavy users were the most vocal early advocates of Cursor; they were also the most damaged by the change.

3. The trajectory implication. Engineers don’t mind paying more for software they trust. They do mind unilateral re-pricing of a product they’d built workflows around. The pricing change implied “Cursor reserves the right to change the deal,” which is a category of trust loss that takes time to repair.

What users actually did

The Reddit threads from June–September 2025 read like a community sorting itself into four buckets:

Bucket 1: Stayed on Cursor, adapted workflows

A 328-upvote thread, “How I use Cursor 10+ hours a day without torching my Claude Opus 4.6 limits”, documents the new survival playbook:

• .cursorrules with explicit “don’t explain code, just output it” — saves thousands of output tokens per day
• Bring-your-own API key routing through LLM Router Gateway, with model selection per task type
• Cheap models (DeepSeek, Gemini Flash) for routine work; Claude Opus reserved for hard tasks

This bucket essentially treats Cursor as the IDE shell while routing the actual AI work to your own choice of model.

Bucket 2: Migrated to Claude Code (in a terminal alongside the editor)

This became the most common response among engineers who care about agent quality. Claude Code in a terminal pane, Cursor reduced to the role of “free or near-free IDE for tab completion.” Many users dropped Cursor Pro entirely and rely on Claude Pro/Max plans for the heavy work.

Bucket 3: Returned to VS Code + Copilot

A smaller but visible group: users who decided AI coding was fine without Cursor’s polish. GitHub Copilot at $10/month with no surprise overages is the safer bet for these users.

Bucket 4: Switched to Windsurf / OSS alternatives

Smaller still: users who tried Windsurf (at $15/month, intentionally cheaper than Cursor), or moved to OSS forks like Cline / Roo / Kilo Code.

What Cursor’s apology did and didn’t do

The July 4 apology refunded users who’d been blindsided by the change. It introduced clearer tier structure. It explicitly acknowledged “we didn’t communicate this well.”

What it didn’t do:

• Restore the old “unlimited slow” tier (it’s gone)
• Walk back the pricing change’s direction (just the rollout)
• Re-acquire trust from users who already migrated

The apology was sincere by SaaS-company standards and earned some goodwill back. But the migration that happened in June–July largely stuck. The Reddit signal in September 2025 includes ongoing “is it safe to come back?” threads that suggest the trust recovery is partial and slow.

What this means for the AI IDE market

Three structural shifts that are now visible:

1. Cursor is no longer the unchallenged default. Through 2024 and Q1 2025, Cursor was the obvious answer for “which AI IDE should I install?” After June 2025, the question has a more complicated answer — and Claude Code, Windsurf, and even Copilot have all gained real consideration share.

2. The Cursor + Claude Code combo emerged as the consensus power-user setup. See our Claude Code vs Cursor comparison for the full take. The combo predates the pricing crisis but the crisis accelerated its adoption — heavy users moved their agent work to Claude Code precisely because Cursor’s pricing made keeping that work in Cursor uneconomical.

3. Pricing is now a feature. Engineers care about pricing model predictability in a way they didn’t when AI coding tools were new and cheap. Cursor’s shift made everyone realise that pricing structure is a long-term commitment, not a temporary detail. Tools that signal stable pricing now have a marketing advantage they didn’t have a year ago.

What the YouTube creators landed on

The most-watched independent explainer of the crisis was Robin Ebers’ “You Won’t Believe What Cursor AI Just Did (NEW UPDATE)” (20 min, 87K views, July 5). His framing of what actually broke is the cleanest articulation of the working-engineer position: “Cursor used to be a simple $20 a month company. It would give you 500 fast requests per month… and even if you would go past these 500 fast requests, Cursor would give you an unlimited what they called slow requests… the point is you had a truly unlimited AI coding experience for $20 a month. And let’s be honest, anyone that knows what the AI coding actually costs behind the scenes knew from the get go that $20 a month is completely unsustainable.”

That second sentence is the one most heated Reddit posts missed. The economics never made sense. The crisis was that the unsustainability surfaced as a unilateral mid-relationship re-pricing rather than as a clearly-signalled transition. Ebers walks through the specific sleight-of-hand that made it worse: Cursor quietly changed the Pro plan’s documentation from “unlimited agent requests” to “extended limits on agent” — a change he calls “honestly… I don’t know who approved this.” The communication mismatch between the public-facing copy and the actual billing model was the trust-breaking move.

His other valuable contribution is the auto-mode caveat: after the rollout, Cursor restored “unlimited” access but only on auto mode where you do not control which model handles your request. “The problem with the auto mode is that you no longer have a preferred model. That means that you could end up with ChatGPT, Grok, Sonnet, Gemini, or even Cursor’s own model because they’re really not clear and transparent about what auto really means. All they say is that your request is being routed to the model with the most capacity, whatever that means.” For users who specifically wanted Claude Opus or GPT-5, “unlimited auto” was not actually what they had paid for.

Solo Swift Crafter’s “Cursor’s Pricing Drama Explained” (15 min, July 6) is the more level-headed second-day take, walking through the same timeline with more measured framing. Useful if you want the events without the editorial voice.

The bigger lesson

The Cursor pricing crisis is a case study in what breaks SaaS trust. Three things, in order:

• Unilateral re-pricing of an existing customer relationship. Customers expect prices to go up eventually; they expect to be talked through it, not surprised by it.
• Communication that minimised the change. Honest math would have prepared users for the impact. Marketing-tinted math made the discovery worse.
• A multi-month iteration cycle on the apology and the new tiers. Each adjustment reminded users that the situation was unstable.

Cursor is still a great product. The team will likely retain dominant market share through the rest of 2025. But the structural change — that “Cursor is the obvious default” stopped being obvious — is unlikely to fully reverse. The pricing model that emerged is structurally less generous than 2024’s, even after the apology adjustments.

For the head-to-head on what to use instead, see our Cursor alternatives after the pricing changes piece and the more comprehensive Claude Code vs Cursor comparison.