Cursor’s pricing apology: what changed, what didn’t, and the community read
Two weeks after the June pricing crisis, Cursor apologised and adjusted tiers. The community read is mixed — partial trust recovery, structural damage stays.
Two weeks after the June 2025 pricing change broke community trust (covered in our Cursor pricing crisis analysis), Cursor published an apology, reported by TechCrunch. Refunds for unexpected charges, new tier explanations, an explicit acknowledgement that “we didn’t communicate this well.”
Here’s the working read on what the apology bought back, and what it didn’t.
What the apology actually delivered
Refunds for the gap period (mid-June to early July). Users who got surprise bills got refunded. The amount was generous in some cases — full refunds for users who’d auto-mode burned through their tier in days.
Clearer tier explanation. The post outlined Pro / Business / Ultra tiers with explicit usage limits, no marketing-tinted language about “unlimited” anywhere.
A direct acknowledgement of fault. Not a “we regret any inconvenience” non-apology — Cursor’s post explicitly said the communication was bad and the rollout was rushed.
By SaaS-apology standards, this is genuine. Anysphere (Cursor’s parent company) handled the response better than the original change.
What the apology didn’t do
It didn’t restore the old “unlimited slow” tier. That tier is gone permanently. The economic structure of the new pricing stands.
It didn’t recover the migrated users. Engineers who moved to Claude Code, Copilot, or Windsurf during the crisis largely stayed migrated. The “back to Cursor” return rate visible on r/cursor is much lower than the “leaving Cursor” rate that preceded it.
It didn’t fully repair trust. A recurring theme in r/cursor threads through July: “I’ll come back if I see they’re stable for six months.” The honeymoon assumption is gone.
The Reddit signal in late July
The community sentiment by late July 2025 settles into three camps:
Camp 1 — stayed and adapted: Users who hardened their workflow (BYOK routing, .cursorrules discipline, careful model selection) and decided Cursor was still worth it. This camp is large but quiet — they’ve moved past the drama.
Camp 2 — migrated and committed: Users on Claude Code + minimal Cursor or pure Copilot. They aren’t coming back unless something specific pulls them. This camp is vocal in “I don’t miss it” threads.
Camp 3 — still evaluating: Users who reduced their Cursor subscription, are testing alternatives part-time, haven’t committed. The largest camp in raw numbers and the one Cursor most needs to recapture.
What Cursor needs to do next
Reading the community signal, the moves that would actually restore trust:
- Six months of stable pricing. No more changes. The community needs to see a quiet quarter.
- Better usage telemetry. Users want to see “you’ve used $14 of your $20” before they hit the wall, not after.
- A real free tier upgrade. Currently the free tier is throttled enough that evaluation is hard. Letting users genuinely test Pro features for longer would help.
- A documented pricing principle. “Here is the long-term math behind how we price; this is what changes and what doesn’t.” Reduces fear of next change.
Whether Cursor will do these is unclear. The team is execution-strong; the pricing model that emerged is structurally what it needs to be financially. Trust recovery will be slow either way.
The bigger pattern
Pricing trust, once broken, is sticky. SaaS-customer relationships are mostly built on the expectation that the deal is the deal. Unilateral changes to the deal — even justifiable ones — break that. The recovery isn’t about the new price; it’s about demonstrating the new price won’t change again.
For where the community actually went, see our Cursor alternatives piece. For the deeper history, the Cursor pricing crisis analysis covers the timeline in detail.
Sources
Every reference behind this piece. If we make a claim, it's because at least one of these said so — or we lived it ourselves.
- Firsthand Tracked Cursor through the apology window
- Blog TechCrunch — Cursor apologizes for unclear pricing changes — TechCrunch
- Blog r/cursor — community sentiment threads through July — r/cursor
- Changelog Cursor June 2025 pricing post (original) — Cursor