ACP standardizes the bridge between editors and coding agents

ACP targets a concrete integration gap in the coding-agent stack: editors and coding agents need a shared protocol so each agent does not have to build a bespoke client integration. The repository describes ACP as a standard for communication between code editors and coding agents, with schema artifacts, JSON-RPC envelopes, request/response/notification types, protocol-version negotiation, and capability-driven compatibility. For agent builders, the practical signal is to separate the agent runtime from the editor client contract and evaluate whether integrations can be reused across IDEs without hiding approval, state, or capability boundaries.