Title: Feature Request: Add support for Agent Client Protocol (ACP)
Is your feature request related to a problem? Please describe.
Claude Code is a powerful agentic coding assistant, but its usage is currently focused on its dedicated terminal REPL and specific IDE integrations. This requires bespoke integration work to expand its reach to other development environments.
With the recent launch of the Agent Client Protocol (ACP) by Zed Industries, a new open standard for communication between code editors and AI agents is emerging. Without supporting this standard, Claude Code may miss the opportunity to be easily integrated into a growing ecosystem of ACP-compatible editors, limiting its potential user base.
Describe the solution you'd like
I propose that Claude Code implements the server-side of the Agent Client Protocol, allowing it to function as an ACP Agent.
This would enable any ACP-compatible client (like the Zed editor or Neovim via the CodeCompanion plugin) to use Claude Code as its backend agent. This would drastically increase Claude Code's accessibility and interoperability with other developer tools.
A potential implementation could be a new CLI command, similar to the existing claude mcp serve:
This command would start Claude Code in a mode that listens for and responds to ACP requests over stdio, as defined by the protocol specification.
Describe alternatives you've considered
The alternative is to continue building and maintaining custom integrations for each new editor or IDE. While this allows for tightly integrated features, it's less scalable and doesn't leverage the network effects of an open standard. The community would also have a much harder time integrating Claude Code into their preferred tools.
Additional context
The Agent Client Protocol (ACP) is an open standard designed to be the "Language Server Protocol (LSP) for AI agents." It standardizes communication for common agentic tasks.
Key features of the protocol that align well with Claude Code's capabilities include:
- JSON-RPC over stdio: A familiar and robust communication method.
- Session Management: Handles creating, loading, and managing distinct conversations.
- Tool Calls & Permissions: A structured way for the agent to report tool usage and request user permission, which maps well to Claude Code's existing security model.
- File System Access: Defined methods for the agent to read/write files via the client.
- Agent Planning: A mechanism for the agent to communicate its step-by-step plan to the client UI.
Early adopters like Google's Gemini CLI have already implemented ACP support. By joining them, Anthropic can position Claude Code as a leader in the open, interoperable AI agent ecosystem. This feature would be a massive win for developers who want to use Claude Code's power within their editor of choice.
Thank you for considering this important feature request
Title: Feature Request: Add support for Agent Client Protocol (ACP)
Is your feature request related to a problem? Please describe.
Claude Code is a powerful agentic coding assistant, but its usage is currently focused on its dedicated terminal REPL and specific IDE integrations. This requires bespoke integration work to expand its reach to other development environments.
With the recent launch of the Agent Client Protocol (ACP) by Zed Industries, a new open standard for communication between code editors and AI agents is emerging. Without supporting this standard, Claude Code may miss the opportunity to be easily integrated into a growing ecosystem of ACP-compatible editors, limiting its potential user base.
Describe the solution you'd like
I propose that Claude Code implements the server-side of the Agent Client Protocol, allowing it to function as an ACP Agent.
This would enable any ACP-compatible client (like the Zed editor or Neovim via the CodeCompanion plugin) to use Claude Code as its backend agent. This would drastically increase Claude Code's accessibility and interoperability with other developer tools.
A potential implementation could be a new CLI command, similar to the existing
claude mcp serve:This command would start Claude Code in a mode that listens for and responds to ACP requests over stdio, as defined by the protocol specification.
Describe alternatives you've considered
The alternative is to continue building and maintaining custom integrations for each new editor or IDE. While this allows for tightly integrated features, it's less scalable and doesn't leverage the network effects of an open standard. The community would also have a much harder time integrating Claude Code into their preferred tools.
Additional context
The Agent Client Protocol (ACP) is an open standard designed to be the "Language Server Protocol (LSP) for AI agents." It standardizes communication for common agentic tasks.
Key features of the protocol that align well with Claude Code's capabilities include:
Early adopters like Google's Gemini CLI have already implemented ACP support. By joining them, Anthropic can position Claude Code as a leader in the open, interoperable AI agent ecosystem. This feature would be a massive win for developers who want to use Claude Code's power within their editor of choice.
Thank you for considering this important feature request