Claude Code hits ACP gap in Zed

Hot take: this looks more like a protocol mismatch than a model problem. Zed’s official Claude Code path is ACP-native and adapter-driven, so pointing the editor at a terminal binary will only approximate the full experience.

• –Zed says Claude Code runs through ACP and a managed adapter, which is how it gets multibuffer diffs, file context, and agent following.
• –Zed’s docs also note that some Claude Code slash commands still depend on SDK parity, which explains why a terminal-style setup can feel incomplete.
• –If the goal is a local llama.cpp-backed workflow, the missing piece is likely a Claude Code-compatible adapter or custom ACP client, not more terminal glue.
• –The post is a good reminder that editor-agent interoperability is becoming the real battleground, not just raw model quality.