Claude Agent via Zed External Agents

What is Claude External Agents?

"Claude External Agents" is best understood as Claude Agent running as a Zed External Agent through the Agent Client Protocol, not as a separate standalone product name documented by Anthropic. Zed's documentation calls this path "Claude Agent" and describes it as the option to use when you want Claude running as an ACP-integrated External Agent inside Zed.

In this workflow, Zed provides the editor-side experience: the Agent Panel, Threads Sidebar, external-agent thread hosting, thread history, and ACP integration. The Claude Agent itself owns its own runtime, authentication, billing, model selection, tools, and Claude-native configuration.

How It Works

Zed External Agents integrate through the Agent Client Protocol, a protocol designed to standardize communication between editors or IDEs and coding agents. ACP is intended to reduce the need for one-off integrations between every editor and every agent.

For local agents, ACP documentation describes JSON-RPC over stdio. For remote agents, the ACP documentation says HTTP or WebSocket can be used, while noting that full remote-agent support is still a work in progress. Zed's Claude Agent page does not document a Claude-specific command, transport endpoint, or config block.

Features

• Runs Claude as an External Agent thread inside Zed.
• Uses Zed's Agent Panel and Threads Sidebar as the host UI.
• Installed through Zed's ACP Registry according to Zed documentation.
• Supports a separate Claude Agent authentication and billing boundary from Zed Agent.
• May use Claude Code auth and Claude-native configuration where supported.
• Claude-specific files such as CLAUDE.md may be read by Claude Agent directly.
• Zed-configured MCP servers may be forwarded to External Agents over ACP, while the agent may also read its own native MCP configuration.
• External Agent threads can be inspected through ACP logs for debugging.

Setup and Authentication

Zed documents the setup at a high level rather than as a CLI command. The documented path is to install Claude Agent from the ACP Registry, then start a Claude Agent thread from the Agent Panel or Threads Sidebar. To choose a billing method, open a Claude Agent thread, run /login, and authenticate with an API key or with Claude Code where supported.

An Anthropic API key configured for Zed Agent does not automatically configure Claude Agent. Zed also states that External Agents run through their own provider relationship, so billing, legal terms, retention, and data handling are between the user and the agent provider. Zed does not charge for External Agents.

Relationship to Claude Code

Claude Code is Anthropic's native agentic coding tool that runs in the terminal, understands a codebase, executes routine tasks, explains complex code, and handles git workflows through natural language commands. Zed's AI by Company page distinguishes Claude Agent via ACP from Claude Code CLI: Claude Agent via ACP is hosted in Zed as an External Agent thread, while Claude Code CLI is run directly in a terminal or Terminal Thread.

This means Claude Agent via Zed is best for users who want Claude-style coding assistance inside Zed's agent UI, while Claude Code remains the more direct Anthropic CLI workflow.

Configuration Boundaries

Zed emphasizes that External Agents have a clear configuration boundary from Zed's built-in agent. Model/provider configuration, auth, API keys, subscriptions, native skills, native instructions, native MCP configuration, and native tool permissions are usually owned by the External Agent unless the integration says otherwise.

Zed Agent profiles do not automatically apply to External Agent threads. Zed Skills do not apply as Zed Skills. Zed MCP servers may be forwarded over ACP, but whether an MCP tool appears can depend on both Zed's MCP configuration and the agent's own native MCP configuration.

Use Cases

Claude External Agents are useful for developers who prefer Zed as their main coding environment but want Claude to operate as an autonomous or semi-autonomous coding agent inside the editor. Typical scenarios include codebase exploration, implementation planning, multi-file edits, refactoring, debugging, and continuing agent threads from Zed's sidebar-based workflow.

Limitations and Caveats

The official Zed documentation does not publish a Claude-specific ACP command, JSON configuration block, installation package name, or exact transport setting for Claude Agent. It also does not document a standalone pricing page for Claude Agent inside Zed. Billing and authentication are described as owned by Claude/Anthropic rather than by Zed.

Because "Claude External Agents" is not presented as a formal Anthropic product page, this entry should be treated as a directory entry for the Zed External Agents integration path for Claude Agent.