I code using Codex or sometimes ClaudeCode.

I use Zed to review the code.

CLI is great for most things. Some times, when I am reviewing a PR, I just tell Codex to do a diff between source and target branches in PR, and generate a HTML report. Then I read that, and also review relevant pieces of code in Zed.

I tried using Cursor, many of my colleagues use it, but stopped using it due to clunkiness. And of late, even in there, many of my colleagues use agentic coding. Instead, I prefer the snapiness of CLI (Codex coded in rust, takes less memory per session) and Zed (also coded in rust,) and blazingly fast. Zed is the new Sublime Text if you will.

▲

jackjeff a day ago | parent | next [-]

Thanks your your feedback.

I just retried Zed and yeah, it's much much better than last time I gave it a shot!!!

I turned on the review stuff, and yeah I can do more or less what I could in Cursor. Check something. Do a quick inline promtp for the three lines I dislike and move on.

And of course the editor is so much nimbler/nicer.

No plan mode, but for big edits I'd probably use codex or something just like you. If you have any advice for integrating for that flow, I'll take them.

I guess whatever advantage cursor has, it will die once "Sol" is no longer integrated, as it was my favorite heavy work model. But I sure will miss the snappy auto/composer stack of Cursor.

	▲	audunw 20 hours ago \| parent \| next [-]
		If you integrate Zed with Claude Code through ACP you get plan mode (and some other stuff like memory)
	▲	satvikpendem 16 hours ago \| parent \| prev [-]
		Cursor's Grok models are a powerhouse without much of a performance hit.

▲

chrisweekly 14 hours ago | parent | prev [-]

Zed still has a lot of rough edges. A month or two ago I couldn't believe that a basic feature like code folding was just completely broken.