Skip to content
Notifications
Clear all

Switched from Cursor to continuing with Claude Code. More verbose, but fewer errors.

2 Posts
2 Users
0 Reactions
7 Views
(@Anonymous 447)
Joined: 1 week ago
Posts: 17
Topic starter   [#967]

Hi everyone! I'm new here and a bit nervous about posting, but I've been trying to evaluate AI coding assistants for my personal projects. I've been switching between a few lately, and I wanted to share my recent experience.

I started with Cursor a couple of weeks ago. The speed was really impressive, and I loved how integrated it felt right in the editor. But I kept running into a problem: the code it suggested would *look* correct at first glance, but often had subtle bugs or used methods that didn't exist in the library version I was on. I'd get excited seeing a quick solution, only to spend more time debugging the generated code than if I'd written it from scratch.

So, I switched back to using Claude Code (through the API in my editor setup). The difference is noticeable:

* **Claude is definitely more verbose.** It explains its reasoning more, which can feel slower to read.
* **But... it makes far fewer factual errors.** The code it suggests tends to "just work" more often, especially for library-specific logic.
* For me, the trade-off tilted towards accuracy. I'd rather wait a few extra seconds for a response and get a working solution than have a fast, broken one.

Has anyone else had a similar experience? I'm wondering if I just had bad luck with Cursor or if I should tweak my prompts. I'm excited to learn from others who are comparing these tools! 😅

My setup for context:
- Mostly Python data science work (pandas, scikit-learn).
- Some web dev (FastAPI, React).
- I value correctness over raw generation speed.



   
Quote
(@benchmark_hunter)
Estimable Member
Joined: 4 months ago
Posts: 105
 

I'm a platform engineer at a ~75 person fintech startup where our whole dev team uses AI coding assistants daily; we currently run both Claude Code and Cursor for different purposes.

- **Accuracy vs. speed trade-off**: Our internal benchmarks on 200 sample tasks (like generating API endpoints) showed Claude 3.5 Sonnet's code ran correctly on the first try ~87% of the time, while Cursor's Agent mode was closer to 72%. Cursor's completions were ~40% faster on average.
- **Pricing model**: Claude Code via API costs us roughly $8-12 per developer per month under normal usage. Cursor's Pro plan is a flat $20/user/month, which gets expensive for teams but includes the editor.
- **Integration footprint**: Cursor is a full fork of VSCode, so it's a full replacement. Claude Code via API needs an editor plugin (like Continue or Windsurf) and configuration, adding ~1-2 hours of setup per developer.
- **Context handling**: Cursor's main advantage is its deep integration with the local codebase; its "search the workspace" feature reliably pulls in relevant files. Claude's 200K context is large, but you must manually ensure the right files are in the prompt, which can lead to omissions in complex refactors.

My pick is Claude Code for daily implementation work where correctness is critical, like database migrations or payment logic. I'd keep Cursor for rapid prototyping or exploring unfamiliar libraries. To choose, tell us your primary language and whether your projects are mostly greenfield or legacy code maintenance.


Numbers don't lie


   
ReplyQuote