ACP Clients & Compatible Coding Agents
Choose an Agent Client Protocol client, connect a compatible coding agent, and confirm that both sides support the capabilities your workflow needs.
Client
The user-facing host
An editor, IDE, terminal, desktop app, web UI, or other interface.
Agent
The coding intelligence
A coding agent that implements ACP directly or through an adapter.
Protocol
The shared contract
JSON-RPC messages, sessions, updates, permissions, and negotiated capabilities.
ACP Clients: Editors, IDEs & Interfaces
ACP client support is broader than a single editor. The official directory also tracks terminal, desktop, web, notebook, mobile, messaging, framework, and connector projects.
- Zed and JetBrains IDEs
- Neovim through CodeCompanion, agentic.nvim, Avante, and other plugins
- Visual Studio Code and compatible IDEs through ACP extensions
- Emacs, Obsidian, Qt Creator, Visual Studio, Pulsar, and Unity integrations
- CLI and TUI clients for terminal-first workflows
- Desktop and web workbenches for parallel agent sessions
- Notebook, mobile, and messaging integrations
- Frameworks and connectors that bridge ACP to other transports and interfaces
ACP-Compatible Agents & SDKs
Some agents implement ACP directly; others use maintained adapters. The registry focuses on agents that advertise valid authentication methods during the ACP handshake.
- Codex CLI through the maintained codex-acp adapter
- Claude Agent through the ACP SDK adapter
- Gemini CLI and GitHub Copilot CLI
- Docker cagent, Goose, Junie, Cursor, OpenCode, Kimi CLI, and Qwen Code
- TypeScript SDK for JavaScript and Node.js integrations
- Rust SDK and protocol schema crates
- Official Python, Java, and Kotlin SDKs
- Capability negotiation for optional client and agent features
How to Check ACP Compatibility
A listing is a starting point. Validate the transport, authentication, and negotiated capabilities for the exact client-agent pair you plan to use.
Pick a client surface
Choose the editor, IDE, terminal, or app where you want to work.
Check the agent distribution
Confirm whether the agent is native, packaged, or connected through an adapter.
Review capabilities
Look for session loading, file operations, terminal access, permissions, and authentication support.
Use stable v1
Prefer ACP v1 for production integrations; treat v2 as experimental until it stabilizes.
ACP Client & Agent FAQ
Quick answers for choosing or building an ACP integration.
An ACP client is the user-facing application that connects to a coding agent. It is often an editor or IDE, but it can also be a terminal, desktop app, web interface, notebook, or messaging integration.
An ACP agent is a coding agent that exposes the Agent Client Protocol. Local agents commonly run as child processes and communicate over JSON-RPC on standard input and output. Remote transports are also being developed.
Yes. Codex CLI and Claude Agent are available to ACP clients through maintained adapters. Check the adapter documentation and client capability support before choosing a setup.
ACP v1 is the current stable wire protocol. ACP v2 is a draft, so production integrations should use v1 unless they intentionally opt into experimental v2 work.
Ready to Go Deeper?
Read the stable protocol overview for message flow and capability negotiation, or return to the ACP guide for the architecture and integration model.