---
title: "Agent Client Protocol"
canonical: "https://canmyagentuse.com/specs/acp"
contentKind: "specification"
locale: "en"
description: "Protocol connecting coding agents to editor and client hosts through directional JSON-RPC roles."
llmSummary: "ACP connects coding agents and editor clients. Local stdio is established while remote transport work evolves, so role, transport, and revision must be explicit."
publishedAt: "2026-08-28T00:00:00.000Z"
updatedAt: "2026-08-28T00:00:00.000Z"
verifiedAt: null
tags: ["acp","editor","coding-agent","protocol"]
---

# Agent Client Protocol

ACP connects coding agents and editor clients. Local stdio is established while remote transport work evolves, so role, transport, and revision must be explicit.

- HTML: https://canmyagentuse.com/specs/acp
- JSON: https://canmyagentuse.com/api/v1/specs/acp.json
- Markdown: https://canmyagentuse.com/specs/acp.md

ACP defines a boundary between coding agents and clients such as editors. Client and agent are asymmetric roles; a product can participate in one without implementing the other.

Assertions should identify role, transport, protocol revision, distribution method, and target release. A CLI flag or registry listing is not by itself full protocol conformance.

## Revision identity

- Authority: ACP / Zed ecosystem
- Revision: living
- Maturity: active
- Structure: JSON-RPC; local stdio established and remote transport evolving
- Canonical specification: https://agentclientprotocol.com/overview/introduction
- Roles: client, agent