upvote
Claude Code is where you move up one abstraction layer. Almost everyone using it productively has spend a lot of time working on their harness, ensuring that everything is planned out and structured such that all that is left is really type in the code. This typically works without error. Before that, you interact a lot via Claude Code in whatever abstraction you feel is right.

That's basically it. You can review changes afterwards, but that's not the main point of Claude Code. It's a different workflow. It's built on the premise: given a tight and verifiable plan, AI will execute the actual coding correctly. This will work, mostly, if you use the very best models with a very good and very specific harness.

Cursor, same as Copilot, has been used by people who are basically pair programming with the AI. So, on abstraction down.

I have no idea what is better, or faster. I suspect it depends at least on the problem, the AI, and the person.

reply
> Cursor, same as Copilot, has been used by people who are basically pair programming with the AI. So, on abstraction down.

This is not really true anymore.

Cursor has better cloud agents than Claude. The multi-agent experience is better, the worktree management is better. Tagging specific code or files in chat is better.

It's hard for me to express the level of pain and frustration I feel going from Cursor to Claude / Conductor+Claude / Claude Extension for VS Code, Claude in Zed, etc.

Really hoping Claude puts more energy into Cowork as a competitor for Cursor and Codex.

reply
I think you are still speaking in the lower abstraction in terms of zwaps' provided understanding. "Tagging specific code" or "files" is likely the type of interfacing most Claude Code users are _not_ doing.

Instead they are defining architecture through specs and verification-loops and attempting to one-shot solutions fitting clear tests. On reflection, I personally don't have many prompts with CC referencing files or code directly, rather I speak in specifications I can then track to a given instance of work in review.

This isn't to suggest you can't work at this abstraction in cursor or w/e interface, but the features you suggest are hardly relevant to the divide zwaps is identifying.

reply
I feel like perhaps you haven't used Cursor. I use both CC and Cursor extensively and as far as I can tell there is nothing that the CC agent will do that Cursor won't do just as well (often using Opus as the backend) and at the same time I get the advantage of seeing the changes in a full IDE if I want to. Their new agent-forward UI hides the code if you don't want to see it as much, but I and many others think that it giving me a full, colourful graphical editor to view changes in is a huge advantage.

I'm not telling you to go use cursor, just to help clarify that you can drive both solutions with the exact same approach and skillset and get very similar results - the difference is the UI. I personally like being able to paste screenshots into the agent, etc.

reply
So that sounds like Claude Code is an inferior subset of Cursor. That Cursor can work like Claude Code, but Claude Code is lacking Cursor’s editing capabilities.
reply
It's good to try Claude Code just so you focus on skills, agents, and CLAUDE.md

Then when you go back to Cursor it will still support all of those things in the settings.

Using Cursor you tend to not think about those as much since Cursor does a lot of it for you as part of the IDE integration. But it's good to refine it your own way.

But for the most part there isn't much difference.

reply
Claude Code isn't really "all terminal" if you embed that terminal in your IDE. I still use Cursor (for now), but I embed a CC panel via extension. With this launch of Cursor 3, I'll probably get off Cursor for good. I have zero interest in this.
reply
Curious, why cursor for this? VSCode or pretty much pure open source IDE's have CC integration. Or am i missing something?
reply
You don't have to stop using the IDE just because you are using Claude Code. Using both at the same time is best of both worlds in my experience.
reply
As someone whose work enforced a switch from Cursor to Claude Code, I do keep on top of the code by pairing it with an IDE, tracking/viewing changes etc. There's no real obstacle to using an IDE as you normally would, with Claude Code as a sidecar.
reply
I run Claude Code from Zed. Very nice experience.
reply
I tried that for a couple weeks and it's no where near as well integrated as Cursor. I hope they get there though because I like Zed.

Zed plus Claude feels more like using isolated browser extensions instead of something part of the browser (unless you pay for Zeds AI thing then the integration is marginally better).

reply
deleted
reply