Agent Client Protocol
Apache-2.0 LSP-for-agents: one protocol so any editor can talk to any coding agent
AI Agents / Agents · Apache-2.0 · 4.5k
Reviewed 2026-10-12 · last push 2026-10-18 · repo checked 2026-10-19
What's Good
Apache-2.0 (agentclientprotocol/agent-client-protocol), schema release schema-v1.25.0 (2026-10-09); stable wire protocol version is 1 via `initialize`. Schema crate and versioned JSON Schema artifacts for SDK generators; higher-level Rust runtime crate for implementers. Reuses MCP-style JSON where it fits, plus agent UX types such as diffs. Markdown is the default user-facing text format. Registry of ACP agents and adapters lives under the same org. ★~4.4k.
The Catch
A protocol, not an app — both the editor and the agent must implement ACP before you feel the benefit. Full remote/cloud agent support is still in progress. Schema artifact versions can move without changing wire compatibility, which matters if you generate SDKs from the JSON Schema. Vs MCP (tool/server protocol for model context): ACP is the editor↔agent session protocol; they solve different layers and often ship together.
Verdict
The interoperability bet for coding agents — adopt it when you build an editor or an agent, not when you just want a chat UI.
Embed
Maintainer? Add the badge to your README. It is free, links to this review, and there is no paid version.
Markdown
[](https://stackgems.com/gems/agent-client-protocol)
HTML
<a href="https://stackgems.com/gems/agent-client-protocol"><img src="https://stackgems.com/badge/agent-client-protocol.svg" alt="Agent Client Protocol reviewed on Stack Gems" height="20"></a>