Feature Request: Add support for Agent Client Protocol (ACP)
Status Open
Maintainer reply None cached
Activity 4 comments · opened Feb 9, 2026
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
Please see https://github.com/anthropics/claude-code/issues/6686. Ideally, that ticket should be re-opened and flagged to remain open, as it is one of the most popular feature requests in this project.
Proposed Solution
Implement the feature, per https://github.com/anthropics/claude-code/issues/6686.
Alternative Solutions
_No response_
Priority
High - Significant impact on productivity
Feature Category
MCP server integration
Use Case Example
_No response_
4 Comments
I'd like to point out that the original issue (#6686) had 1) considerably more detail, and 2) 440 👍 / 114 ❤️ reactions. My ticket here is inferior, and I'd strongly encourage the claude-code developers to reopen the original ticket and mark it somehow to prevent the auto-close bot from closing it again.
Your users really want this feature! Please consider re-opening the original issue and protecting it from the bot!
ACP support would help us adopt Claude Code in our in-game-engine agent. +1!
I'm interested in this feature because I'd like to start using https://github.com/xenodium/agent-shell without needing zed's ACP bridge. That's one too many moving parts in an already complex setup. If claude-code had direct ACP support then integration would be trivial.
I would very much like this feature because I already have a custom dashboard that "runs my life". I don't want terminal access to Claude as an external thing, I want ACP access as something I can integrate into my own UI. Gemini already supports this. So does AWS's Kiro.
Sadly, I feel like this is yet another thing that Antrhropic is digging their heels in on (Claude.md vs Agents.md, anyone?), rather than attempting to let user adopt standards. It's very short-sighted.