goose, inside Glueprint.
A local, extensible, open source AI agent that automates engineering tasks. Glueprint runs goose over the Agent Client Protocol it already speaks — adding live sessions on every device, approvals from your phone, parallel worktrees, schedules, and memory.
goose
Block
- Agent
- goose
- Maintainer
- Block
- Connection
- Agent Client Protocol
- Wire format
- JSON-RPC 2.0 over stdio
- Registry version
- 1.41.0
- License
- Apache-2.0
What is goose?
goose is a general-purpose AI agent that runs on a local machine, originally created at Block and now maintained by the Agentic AI Foundation at the Linux Foundation. It is written primarily in Rust with a TypeScript-based desktop app, and ships as a native desktop application, a CLI, and an API. It works with 15+ model providers including Anthropic, OpenAI, Google, Ollama, OpenRouter, Azure, and Bedrock, and connects to 70+ extensions through the Model Context Protocol. The project is licensed under Apache 2.0.
- Apache 2.0, maintained by the Agentic AI Foundation
- Written in Rust with a TypeScript desktop app
- 15+ model providers including Anthropic and Ollama
- 70+ MCP extensions for tool integration
- Native apps for macOS, Linux, and Windows
Best for Developers wanting an open-source, local, model-agnostic agent for automation and engineering tasks.
Sourced from goose's official site and repository.
How Glueprint runs goose
goose connects over the open Agent Client Protocol — one generic adapter implements the protocol's client side, so goose gets the same surfaces as every other harness:
Glueprint spawns goose, not a fork
Glueprint finds the goose 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 goose 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 goose 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 goose 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 goose gains inside Glueprint
Everything below works with the goose 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 goose 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 goose 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 goose next to Claude Code, Codex, and the rest of the ACP fleet in the Command Center. The protocol differs; the surface doesn't.
goose 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 goose 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.
goose + Glueprint, asked plainly
Can I run goose with Glueprint?
Yes. goose is registered in the official Agent Client Protocol registry, and Glueprint implements the protocol's client side. It spawns the goose 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 goose subscription or API key?
No. Glueprint doesn't resell model access. goose 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 goose 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 goose sessions live, lets you send follow-ups, and handles permission approvals from anywhere.
Can I run goose 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.