一种用于将任何编辑器连接到任何代理的协议
The Agent Client Protocol (ACP) standardizes communication between code editors (interactive programs for viewing and editing source code) and coding agents (programs that use generative AI to autonomously modify code).
Learn more at agentclientprotocol.com.
This repository's root Rust crate is agent-client-protocol-schema. It provides the Rust data model for ACP wire messages, including request, response, notification, JSON-RPC envelope, and protocol-version types. Use this crate when you need direct access to ACP protocol types, schema-oriented tooling, or code generation inputs.
If you are implementing a Rust ACP agent or client, start with the higher-level agent-client-protocol runtime crate instead. That crate provides the client and agent runtime APIs for ACP integrations; this schema crate is the lower-level protocol type surface.
Generated JSON Schema artifacts live in schema/v1 and schema/v2. When a schema release is published, the versioned .json files are also attached to the corresponding schema-v* GitHub release, which is the recommended download surface for SDK generators and other release automation.
The Rust crate version and JSON Schema release versions describe the Rust crate and JSON Schema artifacts themselves. The Rust crate is published to crates.io, while the versioned JSON Schema files are attached to GitHub releases rather than published as crates. These versions follow the compatibility expectations of those artifacts: Rust APIs, generated schema structure, artifact layout, and other details that downstream SDKs or code generators may consume.
The current stable ACP protocol version is 1.
ACP wire compatibility is determined separately by the protocol version exchanged during initialize via protocolVersion. The version field in the versioned schema/*/meta*.json files also describes the ACP protocol version that the corresponding schema represents.
This means two versions of the JSON Schema artifacts can describe the same wire-compatible ACP protocol version while having different schema structure for SDK generators. For example, a release might change how definitions are organized, named, or emitted in the JSON Schema in a way that affects downstream code generation without changing the JSON messages exchanged by ACP clients and agents.
Consumers should not infer wire compatibility from the crate or schema release version alone. Use the negotiated protocolVersion to determine the ACP wire protocol shape and breaking-compatibility level. Within a protocol version, use the exchanged capabilities to decide which optional ACP messages and features are supported. Use artifact versions to manage compatibility with this repository's Rust and schema outputs.
acp-kotlin - Supports JVM, other targets are in progress, see samplesjava-sdk - See examplespython-sdk - See examplesagent-client-protocol - See examples/agent.rs and examples/client.rs@agentclientprotocol/sdk - See examples/ACP is a protocol intended for broad adoption across the ecosystem; we follow a structured process to ensure changes are well-considered. Read the Contributing Guide for more information.
This project does not require a Contributor License Agreement (CLA). Instead, contributions are accepted under the following terms:
By contributing to this project, you agree that your contributions will be licensed under the Apache License, Version 2.0. You affirm that you have the legal right to submit your work, that you are not including code you do not have rights to, and that you understand contributions are made without requiring a Contributor License Agreement (CLA).