ACP: The Protocol Powering Kepler

Agent Client Protocol (ACP) is a JSON-RPC 2.0-based standard that enables agentic development environment clients such as GitKraken’s Kepler to communicate with coding-agent harnesses including Claude Code and Codex CLI. Unlike the Model Context Protocol (MCP), which standardizes an agent’s access to third-party services and local tools, ACP manages the relationship between an orchestrating client and an agent, particularly through creating, listing, resuming, and closing conversational sessions. ACP can pass MCP server configurations when starting sessions, supports developing remote-agent connections, and allows client- or agent-specific extensions through an unstandardized `_meta` field that can carry settings and observability data such as tracing information. A forthcoming ACP v2 aims to improve how prompts and agent turns work, allowing users to intervene during an agent’s ongoing work, while implementers are encouraged to support both v1 and v2 through version negotiation to preserve compatibility with existing peers.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.