# agentclientprotocol/agent-client-protocol

A protocol for connecting any editor to any agent

Repository: https://github.com/agentclientprotocol/agent-client-protocol
Canonical: https://ross.abutalabs.com/products/agent-client-protocol
Homepage: https://agentclientprotocol.com
Language: Rust
License: Apache-2.0
License Family: permissive
Last push: 2026-08-26T19:25:33+00:00

## Health v2 (maintenance only)
Score: 81/100 (v2, computed 2026-09-03T02:39:23.370411+00:00)
- activity 99, release rhythm 86, longevity 31
- inputs: {"age_days": 436, "days_push": 7, "days_rel": 13, "gap_med": 2.0, "n_releases_24m": 69}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 4079, forks 356 (observed 2026-08-28T04:08:34.364005+00:00)

## What it is
The Agent Client Protocol (ACP) is an open protocol, with a Rust schema crate and JSON Schema artifacts, that standardizes communication between code editors/IDEs and AI coding agents via JSON-RPC over stdio or remote transports. It decouples editors from agents so any ACP-compatible agent works with any ACP-compatible editor, analogous to how LSP standardized language servers.

## Use cases
- connect a coding agent to any editor without custom integrations
- implement an ACP-compatible AI coding agent in Rust
- build editor support for third-party AI agents
- generate SDKs for the ACP protocol from JSON Schema artifacts
- run AI agents as local subprocesses or remote services from an IDE
- standardize agent-editor communication like LSP did for language servers

## When to choose
- you are building an editor or IDE that needs to talk to multiple AI coding agents
- you are implementing a coding agent and want broad editor compatibility
- you need Rust types or JSON Schemas for the ACP wire protocol
- you want to avoid per-editor, per-agent custom integration work

## When to avoid
- you need a ready-to-use coding agent or editor rather than a protocol library
- your agent only targets a single editor with its own native API
- you need a higher-level runtime API rather than the low-level schema crate (use the agent-client-protocol runtime crate instead)

## Facets
- artifact type: library
- maturity: active
- function: rpc, sdk, serialization, developer-tools
- domain: developer-tools, artificial-intelligence, apis, text-editors
- platform: cross-platform, rust, cli
- tags: agent-client-protocol, -rpc, coding-agents, editor-integration, protocol, schema, lsp-analog, ai-agents

## Member repositories
- agentclientprotocol/agent-client-protocol (main) score 81

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:08:34.364005+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-29T18:23:26.175323+00:00, confidence not recorded.
  - readme: https://github.com/agentclientprotocol/agent-client-protocol (fetched 2026-08-28T04:08:34.364005+00:00, sha bb858d266593)
  - homepage: https://agentclientprotocol.com (fetched 2026-08-29T09:15:21.094342+00:00, sha fdacdb8b44b2)
  - site_page: https://agentclientprotocol.com/rfds/about (fetched 2026-08-29T09:15:21.103323+00:00, sha 884f15a1b7c2)
- Data as of 2026-08-30T08:39:29.467469+00:00.