[sbysb]

> Anyway, you’re right Claude Code is less ergonomic; generally slower.

The secret in my experience is parallelization - Cursor might be faster or have better ergo for a single task, but Claude Code really shines when you have 6 tasks that are fairly independent.

If you treat CC as just another terminal tool and heavily use git worktrees, the overall productivity shoots through the window. I've been using a tool called Ouijit[1] for this (disclosure: the dev is an old colleague of mine), and I genuinely do not think I could go back to using Cursor or any other traditional IDE+agent. I barely even open the code in an editor anymore, primarily interacting through the term with Vim when I need to pull the wires out.

[1]: https://github.com/ouijit/ouijit

[athoscouto]

Cursor can do that well too. Their code review feature usually gives a handful of independent feedbacks. I just trigger agents independently for all of those. Other integrations with Linear and Slack are also very handy to getting into this workflow. Seems like the 3.0 version is aiming at getting better at this use case.

[sbysb]

FWIW I'm not saying Cursor is not capable of this, but that all of the 'Cursor' bits are superfluous, and using tools that bring you closer to the 'bare metal' of the terminal actually give you both more flexibility (I can run Claude Code, Crush, Codex, OpenCode, etc) and remove an entire layer of abstraction that I believe hinders a devs ability to really go all in on agentic engineering.

I started using Cursor and it was my daily driver for a year or two, but I haven't looked back once in regret moving more towards a terminal focused workflow. (Not to mention the pricing of Cursor being absolutely abysmal as well, although often comped by employers)

[59nadir]

You do know they have an agent that runs in the terminal, right?

[Mashimo]

I think intellij idea can git worktree for agents as well.