Live sessions on every surface
Every ACP agent gets the full session treatment: streamed prompts, tool calls, and diffs on desktop, web portal, iOS and Android.
Your agents. Your environment.
43+ agents,one protocol.
Glueprint speaks the Agent Client Protocol, so every ACP-compatible agent — Gemini CLI, goose, Cline, OpenCode, and the rest of the registry — gets live sessions, inline approvals, worktrees, and remote control from any device.
Your provider account. Your code. A workspace to bring them together.
AG-401The integration01 / 05
Your chosen agent.A shared workspace.
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.
Note
A directory, not a gateIf an agent speaks ACP over stdio, Glueprint can run it. The public registry makes compatible agents discoverable.
AG-402Install & connect02 / 05
Make it part ofyour next project.
Set up the integration on each machine where the agent will run.
- 01
Open the ACP catalog
Browse compatible agents under Settings -> Agents on each execution host.
- 02
Install an agent
Glueprint resolves the selected registry distribution and initializes the protocol connection.
- 03
Start a session
Choose the installed agent from a project or worktree; portal and mobile can control the host session afterward.
The process stays on its host. Remote access follows your Glueprint plan and the capabilities of the installed agent.
Help with agent setupAG-403How it works03 / 05
A direct connection.A shared view of the work.
Glueprint adds the workspace around the agent. Its provider account and configuration stay with the CLI.
- 01
One adapter, every ACP agent
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.
- 02
Sessions stream as structure
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.
- 03
Permission requests become approval cards
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.
- 04
The registry keeps the fleet growing
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.
AG-404Compatibility04 / 05
Know what’savailable.
Some features come from Glueprint. Others depend on what the installed agent supports or reports when it connects.
| 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. |
Check the connected agent for its available models, modes, and permissions. Learn about ACP
AG-405Ownership & limits05 / 05
Your tools.Clear boundaries.
Credentials and model access follow the provider. Glueprint brings the surrounding work into one place.
Glueprint surface
Approvals from anywhere
Protocol permission requests route through Glueprint's approval flow — answer them from your phone, not just the machine the agent runs on.
Glueprint surface
Mix harnesses in one mosaic
Tile a Gemini session next to Claude Code and goose in the Command Center. The protocol differs; the surface doesn't.
Glueprint surface
Per-harness analytics
Messages, sessions, and output tokens roll up per harness from session logs — compare your ACP agents against Claude Code and Codex.
Glueprint surface
Worktrees and git built in
Run each agent in its own git worktree with diffs, history, and a three-pane conflict resolver alongside the session.
Glueprint surface
Encrypted to the relay
Remote viewing of ACP sessions rides the same AES-256-GCM envelope encryption as everything else. The relay routes; it cannot read.
AG-406A few useful answersNotes
Before youstart building.
Q.01What 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.
Q.02Which agents work with Glueprint over ACP?
Any agent that speaks the protocol. The official registry currently lists 43 — including Gemini CLI, goose, Cline, OpenCode, Amp, and Qwen Code — and Glueprint's directory is generated from it.
Q.03Is 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.
Q.04Do 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.
Q.05What 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.
AG-407Go to the sourceOfficial resources
Officialresources.
Agent Client Protocol · Official ACP registry; 43 entries in this build; capabilities are validated on the execution host.
AG-408Keep exploringThe same workspace
More agents.The same workspace.
AG-409 The local tier is free
Your next project.A place to begin.
Download once, run on your hardware, scale up to teams when you're ready. No credit card.