Does anybody have experience running Claude Code or Codex in Zed?

Yes - the Claude ACP is nice, as I like to have a view of the code while chatting. Using just the terminal for dense/long running work feels like a handicap imo. It would be great if it supported more commands though!

▲

unshavedyak 7 hours ago | parent [-]

> It would be great if it supported more commands though!

What does it not support? I want to try and figure out if its shortcomings in the ACP/Claude SDK or if it's just features that Zed has yet to support?

▲

wldcordeiro 6 hours ago | parent | next [-]

I feel like it doesn't support some of the commands that manage Claude itself so think `/mcp` `/plugins` etc. Most of the common ones are configured to work though from what I've seen but the ones that do more configuration of Claude seem to be blocked.

▲

dmix 5 hours ago | parent [-]

That is likely a drawback to their ACP wrapper scheme, it helps exposes IDE functionality but they have to keep up with Claude Code functionality in the other direction. VSCode's Claude code plugin is just like using the CLI.

	▲	wldcordeiro 4 hours ago \| parent [-]
		Entirely right it's a limitation to the ACP side. They're in the middle of adding functionality where you can have terminal/CLI threads and ACP threads too. https://github.com/zed-industries/zed/pull/54729

▲

iknowstuff 6 hours ago | parent | prev [-]

Context length is not shown and I dont think you can paste images? Havent tried though

	▲	wldcordeiro 4 hours ago \| parent [-]
		Context usage is in an open PR now! https://github.com/zed-industries/zed/pull/54881 give it a week or two depending on if you want to use stable vs preview releases. I haven't tried pasting images yet either but I have used their context menu that lets you add images.

▲

sodacanner 7 hours ago | parent | prev | next [-]

It works 'well' with Claude Code, but you're going to be missing a lot of features. There's no display for sub-agents/teams, no ability to clear the context without starting a whole new thread window, no ability to view the current context or usage, etc. There's also no built-in ability to view or change the model's current effort level, which I think is a current limitation with the SDK.

I tried it for a bit and it was definitely usable and I got a few features built out, but I eventually moved back to using CC in the terminal. I'm sure they're working on it, though.

▲

maherbeg 6 hours ago | parent | prev | next [-]

It works well but there are a lot of missing features * skill auto complete * custom agents * sub agents * background process management

▲

NortySpock 7 hours ago | parent | prev | next [-]

Does "local Ollama" or OpenRouter count? I fell into using Zed because there was zero sign-up friction when trying to set up a connection to a local Ollama LLM. Literally "drop-down, select the model you want"

Once I got that running on my machine it was also easy (literally a drop-down+ API key) to switch and explore using models on OpenRouter.

▲

edweis 7 hours ago | parent | prev | next [-]

I just run it in the terminal, every time I tried their integration it was missing a feature or it was easier to read on a terminal

▲

bicepjai 7 hours ago | parent | prev | next [-]

I used to run Claude code on terminal on zed. But the memory usage would balloon eating all my ram 128gb and have to kill the session every other day. I moved back to vscode. I don’t know if they addressed it

▲

jeppester 6 hours ago | parent | prev | next [-]

I use it a lot with Claude Code.

It lacks a lot of features, but IMO feels less "busy" than the terminal version, which I like.

Very recently Zed also gained support for parallel sessions, which is nice. In general it's very obvious that a lot of effort goes into improving it, and it gets better with every release.

▲

802e65bc-e259 7 hours ago | parent | prev | next [-]

Works very well - whats your question?

▲

ramon156 7 hours ago | parent | prev [-]

both support ACP. works really well!