What is Agent Client Protocol in Glueprint?
One generic adapter implements the protocol's client side; everything else is data. That's why the supported-agent list can grow without a Glueprint release.
The ACP project maintains the official Agent Client Protocol registry. The directory is generated from it on each deploy; when the live registry is unavailable, Glueprint uses the checked-in snapshot.
The protocol levels the field: each agent gets the same surfaces — sessions, approvals, worktrees, analytics — the day it joins the registry.
Set up Agent Client Protocol on a host.
Installation is host-specific: repeat these steps anywhere this agent should execute. Portal and mobile can control the session afterward, but the process remains on that host.
Open the ACP catalog
Browse compatible agents under Settings -> Agents on each execution host.
Install an agent
Glueprint resolves the selected registry distribution and initializes the protocol connection.
Start a session
Choose the installed agent from a project or worktree; portal and mobile can control the host session afterward.
How the connection works.
Glueprint adds orchestration and shared surfaces without taking ownership of the coding agent or its provider account.
Glueprint implements the client side of the Agent Client Protocol — JSON-RPC 2.0 over stdio. Per-agent differences are just manifest entries (which binary, which flags), so a new agent in the ecosystem is a catalog entry, not an engineering project.
Agent message chunks, tool calls, and tool-call updates arrive as protocol notifications and render as the same live, typed timeline every other Glueprint session gets — watchable from desktop, browser, or phone.
When an ACP agent asks for permission, the protocol's request surfaces as an inline approval card on whatever device you're holding. Approve, deny, or auto-allow — the same governance layer as every other harness.
The ACP project maintains a public registry of compatible agents. The directory is generated from it — every listed agent speaks the same protocol Glueprint already runs.
Capabilities and discovery.
The status labels separate guaranteed integration behavior from features owned or announced by the installed agent.
| Capability | Status | Behavior |
|---|---|---|
| Live sessions on every surface | Supported | Every ACP agent gets the full session treatment: streamed prompts, tool calls, and diffs on desktop, web portal, iOS and Android. |
| Approvals from anywhere | Runtime | Protocol permission requests route through Glueprint's approval flow — answer them from your phone, not just the machine the agent runs on. |
| Mix harnesses in one mosaic | Supported | Tile a Gemini session next to Claude Code and goose in the Command Center. The protocol differs; the surface doesn't. |
| Per-harness analytics | Supported | Messages, sessions, and output tokens roll up per harness from session logs — compare your ACP agents against Claude Code and Codex. |
| Worktrees and git built in | Supported | Run each agent in its own git worktree with diffs, history, and a three-pane conflict resolver alongside the session. |
| Encrypted to the relay | Supported | Remote viewing of ACP sessions rides the same AES-256-GCM envelope encryption as everything else. The relay routes; it cannot read. |
Authentication, ownership, and limits.
Glueprint is the environment around the agent. Credentials, model access, and vendor-specific behavior stay where their owner designed them.
Every ACP agent gets the full session treatment: streamed prompts, tool calls, and diffs on desktop, web portal, iOS and Android.
Protocol permission requests route through Glueprint's approval flow — answer them from your phone, not just the machine the agent runs on.
Tile a Gemini session next to Claude Code and goose in the Command Center. The protocol differs; the surface doesn't.
Messages, sessions, and output tokens roll up per harness from session logs — compare your ACP agents against Claude Code and Codex.
Run each agent in its own git worktree with diffs, history, and a three-pane conflict resolver alongside the session.
Remote viewing of ACP sessions rides the same AES-256-GCM envelope encryption as everything else. The relay routes; it cannot read.
Common questions
What is the Agent Client Protocol?
ACP is an open protocol — started by Zed Industries — that standardizes how editors and hosts talk to AI coding agents: JSON-RPC 2.0 over stdio, with sessions, streamed output, tool calls, and permission requests. See agentclientprotocol.com.
Which agents work with Glueprint over ACP?
Any agent that speaks the protocol. The official registry currently lists 40 — including Gemini CLI, goose, Cline, OpenCode, Amp, and Qwen Code — and Glueprint's directory is generated from it.
Is Claude Code an ACP agent in Glueprint?
No — Claude Code and Codex get native adapters that speak their own CLI protocols, which unlocks harness-specific depth like session resume and reasoning-effort control. See how Glueprint runs Claude Code. Gemini CLI and the rest of the fleet connect over ACP.
Do ACP agents use my existing accounts?
Yes. Each agent CLI authenticates the way its vendor designed — its own login, its own subscription or API key. Glueprint spawns the binary and speaks the protocol; it doesn't sit between you and the model provider.
What if my agent isn't in the registry?
If it speaks ACP over stdio, Glueprint can run it — the registry is a directory, not a gate. Point a catalog entry at the binary and flags and it joins the fleet.