# ACP agents

> Add Gemini CLI, GitHub Copilot, goose, and dozens more agents from the ACP catalog, or connect your own command.

Canonical URL: https://docs.zuse.sh/providers/acp



The Agent Client Protocol (ACP) is an open standard for talking to coding agents over standard input and output. Any agent that speaks ACP can run in Zuse with the same timeline, tool rendering, permissions, worktrees, and review flow as the built-in providers.

Zuse reads the public [ACP registry](https://agentclientprotocol.com/registry) to offer a catalog of agents. It also keeps a cached copy and a bundled snapshot, so the catalog still opens offline.

## Popular agents [#popular-agents]

These agents are in the catalog today. The registry is updated independently of Zuse, so versions and the full list can change.

<Cards>
  <Card icon="<AgentLogo id=&#x22;gemini&#x22; />" title="Gemini CLI" description="Google's official CLI for Gemini. Runs with npx." />

  <Card icon="<AgentLogo id=&#x22;github-copilot-cli&#x22; />" title="GitHub Copilot" description="GitHub's coding agent CLI. Runs with npx." />

  <Card icon="<AgentLogo id=&#x22;claude-acp&#x22; />" title="Claude Agent" description="ACP adapter for Claude. Supports extra accounts." />

  <Card icon="<AgentLogo id=&#x22;codex-acp&#x22; />" title="Codex" description="ACP adapter for Codex. Supports extra accounts." />

  <Card icon="<AgentLogo id=&#x22;goose&#x22; />" title="goose" description="Open-source, extensible local agent. Native binary." />

  <Card icon="<AgentLogo id=&#x22;cline&#x22; />" title="Cline" description="Autonomous coding agent CLI. Runs with npx." />

  <Card icon="<AgentLogo id=&#x22;qwen-code&#x22; />" title="Qwen Code" description="Alibaba's Qwen coding assistant. Runs with npx." />

  <Card icon="<AgentLogo id=&#x22;kimi&#x22; />" title="Kimi CLI" description="Moonshot AI's coding assistant. Native binary." />

  <Card icon="<AgentLogo id=&#x22;junie&#x22; />" title="Junie" description="JetBrains' coding agent. Native binary." />

  <Card icon="<AgentLogo id=&#x22;mistral-vibe&#x22; />" title="Mistral Vibe" description="Mistral's open-source coding assistant. Native binary." />

  <Card icon="<AgentLogo id=&#x22;auggie&#x22; />" title="Auggie CLI" description="Augment Code's agent and context engine. Runs with npx." />

  <Card icon="<AgentLogo id=&#x22;kilo&#x22; />" title="Kilo" description="Open-source coding agent. Native binary or npx." />

  <Card icon="<AgentLogo id=&#x22;amp-acp&#x22; />" title="Amp" description="ACP wrapper for Amp. Needs the Amp CLI signed in." />

  <Card icon="<AgentLogo id=&#x22;opencode&#x22; />" title="OpenCode" description="OpenCode's ACP mode. Native binary." />

  <Card icon="<AgentLogo id=&#x22;grok-build&#x22; />" title="Grok Build" description="xAI's coding agent and CLI. Runs with npx." />

  <Card icon="<AgentLogo id=&#x22;pi-acp&#x22; />" title="pi ACP" description="ACP adapter for the Pi coding agent. Runs with npx." />
</Cards>

The catalog also includes community entries that Zuse adds itself. They're marked **Community**:

| Agent          | What it needs                                                                                                         |
| -------------- | --------------------------------------------------------------------------------------------------------------------- |
| Oh My Pi (OMP) | Node.js 20+ and the `omp` CLI. If `omp` isn't on the host's PATH, set `OMP_ACP_RUNTIME_COMMAND` to its absolute path. |
| Hermes         | Hermes installed on the host with its ACP extra, and a provider set with `hermes model`.                              |
| OpenClaw       | OpenClaw installed on the host and a running, configured Gateway. Tools and MCP run on the Gateway.                   |

## Add an agent [#add-an-agent]

1. Open **Settings → Providers** and find **ACP agents**.
2. Choose **Add**, then search the catalog. Hover an entry to open its source.
3. Choose **Add** on the agent. Zuse picks a distribution for the host, installs it, and tests the connection.
4. If the agent needs sign-in, choose **Sign in** and pick one of the methods it offers. Some open a terminal inside Zuse; others open a sign-in page in your browser.

The new agent appears in the model picker. Each host keeps its own agents, installations, and credentials.

### How agents are installed [#how-agents-are-installed]

| Distribution | What Zuse runs                                       | Host requirement |
| ------------ | ---------------------------------------------------- | ---------------- |
| npx          | The pinned npm package, with an isolated npm cache   | Node.js and npm  |
| uvx          | The pinned Python package, with an isolated uv cache | uv               |
| Binary       | A verified download for your OS and CPU              | None             |

An entry shows **Unavailable** when it has no distribution for the host. Installed versions stay pinned until you choose **Update*&#x2A; from the agent's &#x2A;*…** menu. A failed update keeps the previous version.

## Gemini CLI [#gemini-cli]

Gemini is available only as an ACP agent. Search the catalog for **Gemini CLI** and add it; Zuse runs `@google/gemini-cli` in ACP mode through npx, so the host needs Node.js and npm. Sign in with one of the methods Gemini CLI offers.

Chats you started with the earlier built-in Gemini integration keep their history and provider.

## Use your own command [#use-your-own-command]

Choose &#x2A;*Use a custom command…** at the bottom of the catalog and fill in:

* **Name**: how the agent appears in Zuse.
* **Executable**: the command to launch, such as `my-agent`.
* **Arguments**: separated by spaces, with shell-style quoting, for example `--acp --model "my model"`.
* **Environment**: `KEY=value` pairs separated by spaces, such as `API_KEY=your-key`. Names must start with a letter or underscore.

Zuse launches the command directly, without shell expansion. Environment values go to the host's encrypted credential store, and Zuse shows only the saved variable names afterward. Leave the field blank when editing to keep existing values, or choose **Clear** to remove them.

## Manage agents [#manage-agents]

Each agent's &#x2A;*…** menu has:

* **Test connection**: checks the protocol and discovers models, modes, and commands.
* **Edit**, **Duplicate**, and **Remove**.
* **Add account** (Claude Agent and Codex): a separate configuration with its own sign-in.
* **Update** (catalog agents): installs the latest catalog version.

Turn an agent off with its switch to hide it without deleting conversation history. Setting changes apply the next time the agent process starts; running conversations keep their launch configuration.

## What works [#what-works]

Zuse uses ACP's structured tool information to render file reads, diffs, searches, terminal output, and permission requests. Unrecognized tools keep a generic card. Models and modes come from the agent, and controls it doesn't support are hidden. Image attachments need the agent to advertise image support.

Resuming a saved chat requires the agent to support loading sessions. If it doesn't, Zuse says so instead of silently replacing the history.

Zuse supports ACP over stdio. It doesn't load JavaScript adapter plugins or connect to network ACP endpoints.
