Claude Code: Now in Beta in Zed

TL;DR Highlight

Zed editor now runs Claude Code natively inside the editor via its own open standard ACP — not a one-off integration, but a universal protocol for any AI agent.

Who Should Read

Developers who frequently use Claude Code but find terminal switching cumbersome, or those waiting for Claude Code support to switch from Cursor to Zed.

Core Mechanics

Zed created ACP (Agent Client Protocol), an open standard so any AI agent that implements it can connect to Zed (and any ACP-compatible editor) — not locked to a specific agent.
Claude Code can now run natively within Zed's Agent Panel. Changes across multi-file edits can be reviewed in real-time and accepted/rejected at the code hunk level.
ACP wraps the Claude Code SDK via an adapter. Claude Code runs as an independent process, and the adapter translates its actions into ACP's JSON RPC format for the Zed UI.
The Claude Code adapter source is open-sourced under Apache license. Neovim's CodeCompanion plugin has already adopted ACP, enabling the same Claude Code experience in Neovim.
Gemini CLI is also integrated via ACP. Users can use Claude Code, Gemini CLI, and other ACP-compatible agents side by side in the Agent Panel.
GitHub user Xuanwo built an ACP implementation for Claude Code right after launch, which the Zed team publicly credited. A case of community contribution accelerating protocol adoption.

Evidence

First comments noted it 'feels rushed.' /compact is unsupported so 'Prompt too long' errors with no workaround, Plan mode switching doesn't work, and model switching is impossible — critical limitations for actual use.
Multiple comments pointed out missing features vs CLI: no Plan Mode, no /clear or /new, no model switching, auto-accept not actually auto-accepting. Some said using CLI inside Zed's terminal is better at this point.
SSH remote development doesn't work, making it impractical for developers who primarily use remote environments.
The ACP standardization effort was viewed positively by some: 'Like TLS, OAuth 2.0, and ECMAScript, multiple players building a common standard matures the ecosystem' — ACP is the right long-term direction vs proprietary integrations.
Anthropic Max subscribers ($200/month) using Opus 4.1 raised concerns about API key costs being too high, questioning whether the Zed integration provides a practical path for these subscription users.

How to Apply

If you use Claude Code and want visual confirmation of multi-file refactoring changes, update to the latest Zed and select Claude Code from the Agent Panel's Plus menu. Caveat: Plan Mode and /compact are missing, so test with simple tasks first.
If you primarily use Neovim and need Claude Code editor integration, CodeCompanion plugin already adopted ACP — Claude Code works in Neovim without extra setup.
If developing your own AI agent/tool with editor integration in mind, reference the ACP spec and open-source Claude Code adapter code to make your agent ACP-compatible for automatic connection to Zed, Neovim, and other ACP-adopting editors.

Terminology

ACPAgent Client Protocol. An open protocol standardizing how AI agents and editors communicate. Like USB — 'match this spec and it plugs in anywhere.'

JSON RPCA lightweight protocol for calling functions over the network. Requests and responses in JSON format, commonly used for inter-process communication.

hunkA single block of changed code in a git diff. When accepting or rejecting specific change blocks rather than entire files, you operate at this unit.

multibufferA Zed view that aggregates code snippets from multiple files into a single buffer. Convenient for reviewing only the changed parts without opening files individually.

Plan ModeA Claude Code mode where the agent presents a work plan before making actual code changes and waits for approval. A safety mechanism widely used to prevent unintended large-scale changes.