The Agent Client Protocol (ACP) lets a client app talk to any coding agent that speaks it. Kvistcode is a client: add an ACP agent as a first-class provider, test the connection and run it next to Claude, Codex and Grok.
ACP is an open protocol for connecting coding agents to client applications. Instead of every app writing a custom integration for every agent, a client that speaks ACP can drive any agent that speaks it. The specification and the list of supporting agents live at agentclientprotocol.com.
Agents Kvistcode runs
Agents Kvistcode runs and how it talks to each
Agent
How Kvistcode connects
Claude Code
Claude Code + claude-agent-acp, over ACP
Grok Build
grok agent stdio, over ACP
Gemini CLI
gemini --acp
Goose
goose acp
OpenCode
opencode acp
Your own agent
Any agent that speaks ACP
OpenAI Codex and local models
Codex CLI, via codex app-server (JSON-RPC)
What you get for an ACP agent
It is added as a first-class provider, with a connection test so you know it works before you rely on it.
It runs in its own branch and working copy, like every other agent. Read how worktrees work.
It appears in Mission Control beside Claude, Codex and Grok, so you can see what every agent is doing at once.
Slash-command autocomplete shows that agent’s own commands, and its “auto” mode is used where it offers one.
Agents from different providers in one Mission Control.
Add your own
Install the agent the way its authors describe. Kvistcode’s first-run setup installs Claude Code, Codex and Grok for you.
In Kvistcode, add the agent as a provider and run the connection test.
