After a Month with Claude Code, I Went Back to Cursor
Honestly, just looking at autocomplete speed, Cursor still feels more convenient lol
When using Claude Code on large projects, the context drain is noticeable enough that I eventually went back to Cursor. That said, when quickly building new features, it was really convenient.
Verdict: Claude for small projects, Cursor for maintenance. Is it just me?
8 answers
Well, that's a bit... A one-month trial seems like too short a sample to draw conclusions from, no? And since you didn't mention the project size or language, generalizing seems like a stretch. I've used it for over three months and actually ended up switching over to Claude entirely. Early on I was stressed about context too, but once I organized rules in CLAUDE.md and split work into subagents, it made a clear difference.
Got a source? What exact metric was used to measure this "perceived context" thing?
I totally relate to it eating up context. When you use it in a big monorepo, you can feel it getting dumber the further you go.
Agreed—I also ended up coming back because Cursor absolutely dominates in autocomplete speed lol
For small projects, Claude; for maintenance, Cursor—this is exactly my conclusion. When whipping up new features, nothing beats Claude. But when working on existing code, for some reason Cursor feels more stable.
I disagree. For maintenance in particular, Claude is actually more convenient... It's much better than Cursor autocomplete for having it read legacy code and refactor it, so I'm curious why you felt the opposite.
So true lol. I think using both is the way to go. I use Claude in the terminal and Cursor in the editor, running them side by side.
I used to feel that Claude consumed a lot of context too, but now that the model has been updated, that seems to have become a thing of the past. I'd recommend testing it again with a recent version. I bet it'll feel quite different. And since it really depends on the task, it's hard to draw a conclusion one way or the other.