Cursor
Reddit take
AI summary of the Reddit excerpts below — not a quote
Cursor is widely regarded as a highly integrated AI code editor that excels at codebase-aware prompting and rapid prototyping, often referred to by users as "vibe-coding." While many developers report significant speed increases and praise its auto-complete as best-in-class, a vocal segment of users finds the tool can become a hindrance. These users report that the AI can be overzealous, occasionally deleting functional code or requiring more time to troubleshoot unintended suggestions than it saves in writing.
Pros
- Deep integration with repository context allowing for code-aware prompting
- Superior auto-complete performance compared to many market competitors
- Effective at "vibe-coding" and rapid project building
- Streamlined error fixing by pasting logs directly into the editor
- Smooth performance as an Electron-based application
Cons
- Can be overzealous, sometimes deleting good code while attempting updates
- Potential for productivity loss due to frequent troubleshooting of AI suggestions
- Chatbot assistant performance reported by some to be inconsistent or degrading
- May ignore existing project conventions, such as opting for external CSS over Tailwind
Caveats
- Security risk: One user reported the AI added logging that accidentally captured passwords in production logs
- Effectiveness often depends on providing high-quality guidance via .cursorrules
- The novelty of the AI features may wear off for some professional teams over time
Best for
- Rapid prototyping and building new features quickly
- Developers who want an AI with deep knowledge of their entire codebase
- Users who prefer Claude-based code generation and composition
Avoid if
- You find AI suggestions distracting or feel they slow down your manual coding flow
- You work in a high-security environment where automated logging changes are a risk
- You are sensitive to AI tools making unintended deletions in your source files
This summary uses balanced time weighting with about a 6-month half-life. The evidence is older (median age ~306 days) and comes from a period of high volatility in AI tool development.
Sentiment
36 positive (62%) · 11 mixed (19%) · 11 negative (19%)
Trust + time weighted score: +44% · raw score 43%
What redditors said (10 of 58)
It can also enrich your prompt with more details so you don’t have to build a 5 paragraph prompt from scratch. It’s tightly integrated into whatever workflow. Take Cursor for example.
the staff/principal engineers are slinging PRs like never before thanks to cursor and Claude
When working across Claude Code, Cursor, or Freebuff CLI (which uses GLM 5.2 sessions), raw conversational prompts frequently suffer from context degradation after multiple roundtrips.
This is not meant to replace quick coding assistants. For small edits, Cursor, Claude Code, OpenCode directly, etc. are faster and simpler.
host-agnostic setup: works anywhere that can load skills from a directory (Claude Code, Cursor, Hermes, etc.)
i try to test my prompt iterations in isolated workspaces. i use cursor for setting up python validation loops
i use cursor for writing code, Git for changes, and Runable when i need to generate user manuals or reports.
i’ve noticed the same thing with tools like claude, cursor, even runable to some extent , so like once you give them actual constraints/context instead of random prompts the results get way more consistent
Both Copilot and Cursor are cloud-first and satisfying that requirement with either is either impossible or requires custom infrastructure the vendor doesn't actually support.
The productivity comparison versus Copilot or Cursor is complicated. On raw suggestion quality for greenfield work those tools are better. We can't use them.
Compare
Cursor vs RunableCursor vs Claude CodeCursor vs Visual Studio Code