Acp Bridge

ACP Bridge v0.3.0

Multi-agent orchestrator for OpenClaw and other AI platforms. Manages coding agents (OpenCode, Codex CLI, Claude CLI, Gemini CLI) through the Agent Client Protocol (ACP) — structured JSON-RPC over stdio, multi-agent task execution, dependency chains, and built-in diagnostics.

Why

If you use OpenClaw or orchestrate multiple AI coding agents, you've probably resorted to tmux send-keys / capture-pane hacks. That approach is:

- Wasteful - polling burns tokens on non-semantic terminal output
- Fragile - ANSI escape codes, progress bars, rendering artifacts
- Blind - no reliable way to know if an agent is idle, running, or waiting on approval

ACP Bridge replaces that with a stable HTTP API backed by the Agent Client Protocol (ACP).

How it works

OpenClaw Integration

ACP Bridge is designed to work with OpenClaw — an autonomous AI agent platform. OpenClaw agents can use ACP Bridge to dispatch coding tasks to multiple coding agents (Codex, Claude, Gemini) in parallel, with full permission control and diagnostics.

Typical workflow:
1. OpenClaw agent starts ACP Bridge daemon
2. Spawns coding agents as needed (start codex, start claude, etc.)
3. Sends tasks via ask or creates multi-agent task graphs via /tasks
4. Monitors progress, approves/denies permissions, handles errors
5. Uses doctor and diagnose for automated troubleshooting

Installation

Quick Start

Default daemon address is 127.0.0.1:7800.

Alternative local development flow:

Config File

Create ~/.config/acp-bridge/config.json:

Environment variables like ACP_BRIDGE_PORT and ACP_BRIDGE_HOST still override config file values.

Supported Agents

Adapter Details

Each agent type uses a different path to speak ACP over stdio:

OpenCode - Native ACP. Just works with opencode acp.

Codex CLI - Uses…