Got it. Below is a ranked list from biggest + most frequently reported pain points → smaller / more niche ones, based on volume of complaints across Reddit, Cursor forums, Medium posts, and dev blog reviews, plus how strongly users say each issue hurts their day-to-day work.
This is a severity × frequency sort (not just vibes).
🔥 Tier 1 — Biggest & Most Frequent Pain Points
(These come up constantly and directly break trust or flow)
1. Unreliable / Incorrect AI Edits
Why it’s #1:
Nothing frustrates devs more than an AI that confidently does the wrong thing.
Common complaints
Says it applied changes but didn’t
Modifies the wrong files or sections
Introduces subtle bugs
Deletes or rewrites correct logic
Impact: High trust damage + rework time
Frequency: Extremely high (top complaint on Reddit & forums)
2. Context Loss & “Forgetting” the Task
Why it’s huge:
Cursor is supposed to understand your codebase — when it doesn’t, it feels pointless.
Common complaints
Loses track of what was just discussed
Re-reads docs repeatedly
Forgets earlier decisions in the same session
Acts like a fresh chat after updates
Impact: Breaks long workflows
Frequency: Very high, especially after updates
3. Over-Aggressive or Uncontrolled Code Changes
Why it hurts:
Users feel out of control of their own code.
Common complaints
Touches commented-out code
Reformats or rewrites things not asked for
Makes large, hard-to-review diffs
Agent mode creates “PR soup”
Impact: Review overhead + fear of using automation
Frequency: Very high
⚠️ Tier 2 — Serious, Very Common Workflow Killers
4. Slowness, Lag, and Timeouts
Why it matters:
AI is only helpful if it’s fast.
Common complaints
Slow responses on non-top tiers
Long waits to apply edits
Lag on large repos
Regional latency issues
Impact: Breaks flow state
Frequency: Very common (esp. larger projects)
5. Breakage After Updates
Why users hate this:
Updates feel risky instead of helpful.
Common complaints
New bugs introduced
Behavior changes without warning
Regressions in AI quality
Need to downgrade or workaround
Impact: Lost time + instability
Frequency: Common after major releases
6. Poor Transparency & Communication
Why it compounds everything:
When things go wrong, users feel ignored.
Common complaints
Weak or unclear changelogs
Little acknowledgment of major issues
Slow or vague forum responses
Impact: Erodes goodwill
Frequency: Very common sentiment
🧩 Tier 3 — Medium-Impact, Common Complaints
7. Hard-to-Review Multi-File Changes
Why it’s painful (especially for teams):
Massive diffs
Mixed refactors + logic changes
No clear intent separation
Impact: Slows teams, hurts code quality
Frequency: Common for agent-mode users
8. Pricing, Limits, and Billing Confusion
Why it annoys users:
Changing plans
Unclear usage caps
Perceived mismatch between cost and reliability
Impact: Friction, not a blocker
Frequency: Common but secondary
9. Cursor Overrides VS Code Muscle Memory
Why it’s frustrating:
Shortcut conflicts
UI differences
Workflow disruption for longtime VS Code users
Impact: Annoying but survivable
Frequency: Moderate
🪜 Tier 4 — Lower Frequency or More Niche
10. Not Enterprise-Ready
Issues
Too risky for mission-critical code
Hard to enforce consistency
Not audit-friendly
Frequency: Mostly teams / large orgs
11. Doesn’t Learn User Preferences
Issues
Repeats the same mistakes
Doesn’t adapt to coding style
No long-term memory of corrections
Frequency: Mentioned often, but less urgent
12. Weaker for Backend / Complex Systems
Issues
Inferior to IntelliJ-style tooling
Less helpful for deeply typed or layered systems
Frequency: Backend-heavy users
13. Community Anxiety About Product Direction
Issues
“Feels built for demos”
Focus on hype vs reliability
Frequency: Opinionated but real
🧠 Final Ranked Summary (Top → Bottom)
Unreliable AI edits
Context loss / forgetting
Over-aggressive changes
Slowness & lag
Update-introduced bugs
Poor communication
Hard-to-review PRs
Pricing confusion
Shortcut & UX friction
Not enterprise-ready
No learning from past edits
Backend limitations
Direction / vision concerns
If you want, I can:
🔍 Map these pains to root causes
🆚 Compare this list vs GitHub Copilot / Claude Code
🧪 Translate pain points into product opportunities
📊 Estimate which 3 fixes would reduce churn the most
Just tell me how you want to use this.