Clients

Clients, frameworks, connectors, and related tools around the Agent Client Protocol.

The following projects implement ACP directly, connect ACP agents to other environments, or support adjacent coding-agent workflows.

Editors and IDEs

• Chrome ACP (Chrome extension / PWA)
• Emacs via agent-shell.el
• JetBrains
• neovim
  • through the CodeCompanion plugin
  • through the carlos-algms/agentic.nvim plugin
  • through the yetone/avante.nvim plugin
  • through the hermes.nvim plugin
• Obsidian — through the Agent Client plugin
• Unity ACP Client(Unity plugin)
• Unity Agent Client (Unity editor)
• Visual Studio Code — through the ACP Client extension
• Zed

CLI and TUI

• acpx (CLI)
• Nori CLI
• pool
• Toad

Desktop and Web

• ACP UI (Windows, macOS, Linux, iOS, Android, Web)
• Agent Studio
• AgentRQ — Human-in-the-loop realtime task management and collaboration (Web)
• AionUi
• aizen
• DeepChat
• fabriqa.ai
• gemini-cli-desktop
• Harnss
• Jockey — open-source multi-agent orchestrator (Tauri + Rust + SolidJS) that coordinates Claude Code, Gemini CLI, and Codex CLI via ACP
• Lody
• Minion Mind — through the Agent Client plugin
• Mitto
• Ngent
• RayClaw
• RLM Code
• Sidequery (coming soon)
• Tidewave
• Web Browser with AI SDK (powered by @mcpc/acp-ai-provider)
• Kangaroo — database IDE with Agent Client Protocol support
• ACP Components - A universal frontend component library for building AI Agent interfaces based on the ACP

Notebook and data tools

• agent-client-kernel (Jupyter notebooks)
• DuckDB — through the sidequery/duckdb-acp extension
• marimo notebook

Mobile clients

These mobile-first tools bring ACP and related coding-agent workflows to phones and tablets:

• Agmente (GitHub) (iOS)
• Ferngeist (Android)
• Happy (GitHub) (iOS, Android, Web)
• Mobvibe (iOS, Android, Web)

Messaging

• ACP Discord (Discord)
• duckdb-claude-slack (Slack)
• Juan (Slack)
• OpenACP (Telegram, Discord, Slack) — self-hosted bridge for ACP agents; streams tool calls and responses in real time
• Telegram ACP Bot (Telegram) — through the telegram-acp-bot connector
• Telegram-ACP (Telegram) — Supports multi-thread chat and message streaming
• ACP Router (Telegram) - an ACP client surface for driving ACP agents from Telegram, with rich diffs, approvals and many more.
• WeChat ACP (WeChat)
• Sniptail (Discord, Slack) - self-hosted chat bridge for running coding agents across your team’s repositories
• Lark ACP (Lark/飞书)

Frameworks

These frameworks add ACP support through dedicated integrations or adapters:

• AgentPool — with built-in ACP integration for IDEs and external ACP agents
• fast-agent — through fast-agent-acp
• ACP Kit - adapter toolkit for exposing existing Pydantic AI / LangChain agent runtimes through ACP.
• Koog — through the agents-features-acp integration
• LangChain / LangGraph — through Deep Agents ACP
• LlamaIndex — through the workflows-acp adapter for Agent Workflows
• LLMling-Agent — with built-in ACP support for running agents through ACP clients
• Mastra — through the @mastra/acp package for wrapping external ACP agents as tools or subagents

Connectors

These connectors bridge ACP into other environments and transport layers:

• ACP to AG-UI — bridges any ACP agent to web frontends via AG-UI events over SSE; works with CopilotKit, AG-UI HttpAgent, or custom UIs (Web)
• AgentRQ — bridges stdio-based ACP agents to the AgentRQ - Human-in-the-loop task collaboration service using MCP server.
• Aptove Bridge — bridges stdio-based ACP agents to the Aptove mobile client over WebSocket
• ACP Remote - remote WebSocket transport for ACP agents and clients.
• OpenClaw — through the openclaw acp bridge to an OpenClaw Gateway
• stdio Bus – deterministic stdio-based kernel providing transport-level routing for ACP/MCP-style agent protocols.