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!

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.

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

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.

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

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

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.

Works very well - whats your question?

both support ACP. works really well!