Amp, inside Glueprint.
ACP wrapper for Amp - the frontier coding agent. Glueprint runs Amp over the Agent Client Protocol it already speaks — adding live sessions on every device, approvals from your phone, parallel worktrees, schedules, and memory.
Amp
tao12345666333
- Agent
- Amp
- Maintainer
- tao12345666333
- Connection
- Agent Client Protocol
- Wire format
- JSON-RPC 2.0 over stdio
- Registry version
- 0.8.1
- License
- Apache-2.0
What is Amp?
amp-acp is an open-source adapter, built by an independent developer, that connects Amp Code to clients implementing the Agent Client Protocol, such as Zed and Toad. Written in TypeScript and run on Node.js 18 or newer, it streams Amp messages, tool calls, and thinking output in real time and preserves thread context across prompts. It exposes Amp's smart, deep, and rush modes with configurable reasoning effort, supports image input, and passes through MCP servers configured in the client.
- Apache-2.0 licensed, TypeScript on Node.js 18+
- Bridges Amp Code to ACP clients like Zed
- Real-time streaming of messages and tool calls
- Exposes Amp smart, deep, and rush modes
- MCP passthrough and image input support
Best for Amp Code users who want to drive it from a Zed or other ACP-compatible editor.
Sourced from Amp's repository.
How Glueprint runs Amp
Amp connects over the open Agent Client Protocol — one generic adapter implements the protocol's client side, so Amp gets the same surfaces as every other harness:
Glueprint spawns Amp, not a fork
Glueprint finds the Amp binary you installed and spawns it, then speaks the Agent Client Protocol — JSON-RPC 2.0 over stdio — to drive it. Same CLI, same authentication; Glueprint just wraps the session.
Output streams as structure
Message chunks, tool calls, and tool-call updates from Amp arrive as protocol notifications and render as the same live, typed timeline every Glueprint session gets — watchable from desktop, browser, or phone.
Permission requests become approval cards
When Amp asks to write a file or run a command, the protocol's permission request surfaces as an inline approval card on whatever device you're holding. Approve, deny, or auto-allow per tool.
One adapter, the whole fleet
Because Amp speaks ACP, adding it is a catalog entry, not an engineering project — the same adapter runs every other agent in the registry, so you can tile them side by side.
What Amp gains inside Glueprint
Everything below works with the Amp CLI you have today — no migration, no new account for the model, no lock-in. Uninstall Glueprint and your terminal workflow is exactly as it was.
Live sessions on every surface
Watch every Amp prompt, tool call, and diff stream in real time — desktop, web portal, iOS and Android. The session runs on your machine; the view follows you.
Approve from your phone
Permission prompts arrive as approval cards wherever you are. Kick off a refactor at your desk, approve the file writes from the couch.
Parallel sessions across worktrees
Run several Amp sessions side by side, each in its own git worktree, with diffs, history, and a three-pane conflict resolver alongside.
Mix harnesses in one mosaic
Tile Amp next to Claude Code, Codex, and the rest of the ACP fleet in the Command Center. The protocol differs; the surface doesn't.
Amp as a persistent assistant
Promote it to an assistant: persona, constitution, long-term memory, and a daily journal on disk, loaded into every wake.
Routines on a schedule
Wake it on cron: triage the inbox every 30 minutes, sweep PRs at 9am, run the nightly cleanup. Quiet hours and watermarks prevent re-fires.
Analytics per harness
Messages, sessions, and output tokens computed from session logs — compare Amp against Claude Code, Codex, and your other ACP agents.
Encrypted to the relay
Remote viewing rides AES-256-GCM envelope encryption. The relay routes; it cannot read.
Amp + Glueprint, asked plainly
Can I run Amp with Glueprint?
Yes. Amp is registered in the official Agent Client Protocol registry, and Glueprint implements the protocol's client side. It spawns the Amp CLI you already installed and drives it over JSON-RPC 2.0 — adding live sessions, inline approvals, worktrees, and remote control.
Do I need a separate Amp subscription or API key?
No. Glueprint doesn't resell model access. Amp authenticates exactly the way its vendor designed — its own login, subscription, or API key. Glueprint spawns the binary and speaks the protocol; it doesn't sit between you and the model provider.
Can I run Amp from my phone?
Sessions always run on your machines — a laptop, a desktop, or a server with the headless daemon. The iOS and Android app streams Amp sessions live, lets you send follow-ups, and handles permission approvals from anywhere.
Can I run Amp next to Claude Code and Codex?
Yes — that's the point. Each harness is an adapter; sessions from all of them tile into the same Command Center, share the same task boards, and roll up in the same per-harness analytics.
Is my session content private?
Yes. Remote viewing routes AES-256-GCM-encrypted envelopes through the relay, which stores a wrapped key it cannot open — decryption happens on your devices. On the free local tier, session content never leaves your machine at all. See security.
Bring Glueprint to your workflow.
Download once, run on your hardware, scale up to teams when you're ready. No credit card.