agent-client-protocol

Why we included this project

Any team that builds a coding agent or wires an AI assistant into an editor eventually hits the same wall: every editor exposes its own extension API, and every agent has its own interface. ACP exists to give both sides one protocol. It is JSON-RPC based, ships versioned JSON Schema artifacts, and splits the work into client and server roles, so an editor that implements the client side can talk to any agent that implements the server side without bespoke glue code. The repository also gives you a real starting point: a low-level schema crate for protocol types and code generation, a higher-level Rust runtime crate with client and agent APIs, and versioned schema files attached to releases. For a maintainer who wants an agent to work across editors like Zed, adopting a shared protocol beats hand-rolling another editor-specific integration.