Zed Claude Code: How to Use Claude in the Zed Editor

Zed Claude Code setup: run Claude as an ACP agent or the claude CLI in a Terminal Thread, what works, what doesn't, and how it compares with VS Code.

Josh Pocock7 min read

Zed editor cover

AI Coding

Zed editor

Stride AI Academy

To use Zed with Claude Code, you have two options. You can install Claude Agent from Zed's ACP Registry and chat with it in Zed's Agent Panel, or you can open a Terminal Thread in Zed and run the normal claude command line tool there. There is no official Anthropic extension for Zed. The Agent Panel route runs through Zed's Agent Client Protocol (ACP) and an open source adapter built on the Claude Agent SDK.

This guide covers both setups, what each one supports, the gaps to know about, and how Zed compares with the VS Code extension. Everything here was checked against Zed's External Agents docs, Terminal Threads docs and AI by company page, the claude-agent-acp adapter repo, Claude Code's VS Code docs and Agent SDK commands docs, and Anthropic's support article on the Agent SDK and Claude plans on November 21, 2026.

The two ways to run Claude Code in Zed

Zed's docs list these paths for Claude:

Path Where it runs Who owns sign-in and billing
Claude Agent via ACP An External Agent thread in Zed's Agent Panel Claude and Anthropic
Claude Code CLI A Terminal Thread in Zed Your Claude subscription or Claude Code login
Anthropic API in Zed Agent Zed's own agent, with Claude models Anthropic API billing

The third row is Zed's built-in agent calling Claude models with an API key. It isn't Claude Code, so this guide skips it.

Pick the ACP route if you want Claude's edits shown in Zed's own interface. Pick the Terminal Thread if you want the full Claude Code command line experience, exactly as it runs in any other terminal.

Set up Claude Agent through ACP

ACP is an open protocol that lets an editor talk to an agent running as a separate process. Zed hosts the conversation, and the agent keeps its own login, models and tools.

  1. Open the Command Palette and run zed: acp registry. You can also run agent: open settings, go to the External Agents page, click Add Agent and choose Install from Registry.
  2. Install Claude Agent.
  3. Start a Claude Agent thread from the Agent Panel or the Threads Sidebar.
  4. In the thread, run /login and pick a billing method: an API key, or your Claude Code login where that's supported.

An Anthropic API key you've already added for Zed's own agent doesn't carry over. Zed's docs say Claude Agent owns its authentication and billing separately.

If you start Claude threads often, bind a key to the agent: new external agent thread action in your keymap.

What works in an ACP thread

The adapter that connects Claude to Zed is claude-agent-acp, open source under the Apache 2.0 license. Its README lists support for:

  • @-mentions for context, and images
  • Tool calls, with permission requests
  • Following Claude as it edits, plus edit review
  • TODO lists and nested subagent transcripts
  • Interactive and background terminals
  • Your own custom slash commands
  • MCP servers from the client, including ones Zed forwards over ACP

Claude Agent may also read CLAUDE.md directly, according to Zed's docs, so your project instructions still apply. If you haven't written one yet, see these CLAUDE.md file examples.

Zed can also import past threads from installed External Agents into Thread History. Open the Threads Sidebar, open Thread History with the clock icon, and click Import Threads.

What doesn't carry over

The ACP route is not the same as running claude in a terminal. A few things to expect:

  • Interactive-only commands. The adapter runs on the Claude Agent SDK. Anthropic's SDK docs say commands that need an interactive terminal, such as /theme and /terminal-setup, aren't available there. For the full list of what's built in, see Claude Code slash commands.
  • Zed settings stop at the boundary. Zed Agent profiles and Zed Skills don't apply to External Agent threads.
  • MCP can come from two places. Zed may forward its MCP servers over ACP, and Claude may also read its own MCP config. If a tool is missing, check both. For Claude's side, see how to add an MCP server to Claude Code.
  • Remote projects need checking. Over SSH or in dev containers, Zed's docs say the agent may read credentials locally, remotely or through its own sign-in, so test it on your setup.

When something breaks, run dev: open acp logs from the Command Palette. It shows the messages passing between Zed and the agent.

Run the claude CLI in a Terminal Thread

A Terminal Thread is a terminal that Zed files as a thread in the Threads Sidebar. The CLI inside it works exactly as it does anywhere else, with its own login, models, skills and MCP config.

First, install the CLI if you haven't. Our guide on how to install Claude Code has the command for each system. Then:

  1. Open the new-thread menu in the Agent Panel, using the agent selector on the left or the + icon at the top right.
  2. Choose Terminal.
  3. Run claude.

To have Zed start Claude in every new Terminal Thread, add this to your Zed settings:

JSON
{
  "agent": {
    "terminal_init_command": "claude"
  }
}

Zed sends the command to your shell as if you'd typed it. It also runs when Zed reopens a saved Terminal Thread.

Get notified when Claude needs you

Zed shows a notification when a Terminal Thread rings the terminal bell while it's out of focus. To make Claude Code ring it when a task finishes or it stops for permission, set this in ~/.claude/settings.json:

JSON
{
  "preferredNotifChannel": "terminal_bell"
}

You can also set it inside Claude Code: run /config, open Local Notifications and choose Terminal Bell. If you run Claude inside tmux, add set -g allow-passthrough on to ~/.tmux.conf so the bell reaches Zed.

Two Terminal Thread limits from Zed's docs: Zed's agent profiles, tool permissions, Skills and MCP settings don't apply, and Terminal Threads are closed rather than archived, so they don't appear in Thread History.

Does it use your Claude subscription?

Anthropic's support article, updated October 7, 2026, says that when you sign in with a Claude plan, the Agent SDK and claude -p draw from your subscription limits. Its June 15, 2026 update says Anthropic paused previously announced changes to Agent SDK billing and that third-party app usage still draws from subscription limits.

The Terminal Thread route is the plain claude CLI, so it works the same as in any terminal. For plan limits and API pricing, see how much Claude Code costs.

Zed vs the VS Code extension

The key difference is who builds the integration. Anthropic publishes the Claude Code extension for VS Code. In Zed, Zed built the integration on ACP, and Claude Code's docs have IDE pages for VS Code and JetBrains only. For editors that can't install the extension, Anthropic's docs say to install the CLI and run claude in the editor's terminal.

VS Code extension Zed (ACP or Terminal Thread)
Made by Anthropic Zed, using the open source ACP adapter
Install Extensions view, search "Claude Code" ACP Registry, or run the CLI in a Terminal Thread
CLI included Bundles its own copy for the chat panel ACP adapter runs Claude for you; Terminal Thread needs the CLI installed
Plan review Review and edit plans before accepting Not listed in Zed's docs or the adapter README
File context @-mentions with line ranges from your selection @-mentions in ACP threads
Edit review Diffs in the editor Edit review and following in ACP threads

If you want an editor integration that Anthropic builds and documents, use VS Code. Our VS Code extension guide covers its setup. If you prefer Zed, the ACP route gives you a native-looking panel, and the Terminal Thread gives you the full CLI.

Learn to build with Claude Code

The Stride AI Coding course teaches Claude Code and Codex for building client tools, written for non-programmers, with weekly live calls to review your builds. Many of the free guides cover Claude Code setups, and the Claude Code community is where members compare theirs.

FAQ

Does Claude Code work in Zed?

Yes. You can install Claude Agent from Zed's ACP Registry and use it in the Agent Panel, or run the claude CLI in a Zed Terminal Thread. Anthropic doesn't publish a Zed extension, so both routes go through Zed's own features.

How do I install Claude Code in Zed?

Run zed: acp registry from the Command Palette, install Claude Agent, start a thread and run /login. For the CLI instead, install Claude Code, open a Terminal Thread from the Agent Panel's new-thread menu and run claude.

Is Claude Agent in Zed the same as Claude Code?

It runs Claude through the Claude Agent SDK, which Anthropic describes as Claude Code as a library, but the interface is Zed's. Commands that need an interactive terminal aren't available, and Zed's docs call the Terminal Thread the "native Claude Code experience".

Can I use my Claude Pro or Max plan in Zed?

Anthropic's support article says Agent SDK usage signed in with a Claude plan, and third-party app usage, draw from your subscription limits. In the ACP thread, run /login to choose an API key or your Claude Code login where supported.

Do my MCP servers work with Claude in Zed?

Usually. Zed may forward its own MCP servers to Claude Agent over ACP, and Claude may read its native MCP config too. If a tool is missing, check both, or use a Terminal Thread, where the CLI uses only its own config.

Is Zed or VS Code better for Claude Code?

VS Code has Anthropic's official extension, with plan review and @-mentions with line ranges. Zed works well if it's already your editor, through ACP or the CLI in a Terminal Thread. Pick the editor you use every day.

Build it with us in Stride AI Academy

Four courses, weekly live calls and a community of people building and selling AI. Or start with 320+ free guides.

Keep reading

Free AI Coding guides