Factory Droid, inside Glueprint.
Factory Droid - AI coding agent powered by Factory AI. Glueprint runs Factory Droid over the Agent Client Protocol it already speaks — adding live sessions on every device, approvals from your phone, parallel worktrees, schedules, and memory.
Factory Droid
Factory AI
- Agent
- Factory Droid
- Maintainer
- Factory AI
- Connection
- Agent Client Protocol
- Wire format
- JSON-RPC 2.0 over stdio
- Registry version
- 0.164.1
- License
- proprietary
What is Factory Droid?
Factory Droid is a terminal UI from Factory AI for running AI agents called Droids without leaving the keyboard. It is built around delegation rather than autocomplete, aiming to handle complete tickets and investigations while the user works elsewhere. Sessions persist and can be forked, resumed, and rejoined, and the same work syncs across TUI, desktop, web, IDE, and Slack. It includes a slash-command palette, MCP support, and a portable, shareable Skills framework.
- Built by Factory AI for delegating whole tickets
- Persistent sessions can fork, resume, and rejoin
- Syncs across TUI, desktop, web, IDE, and Slack
- Slash-command palette with MCP support
- Portable, shareable Skills framework
Best for Engineers who want to delegate full tickets to agents across terminal, IDE, and Slack.
Sourced from Factory Droid's official site .
How Glueprint runs Factory Droid
Factory Droid connects over the open Agent Client Protocol — one generic adapter implements the protocol's client side, so Factory Droid gets the same surfaces as every other harness:
Glueprint spawns Factory Droid, not a fork
Glueprint finds the Factory Droid 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 Factory Droid 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 Factory Droid 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 Factory Droid 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 Factory Droid gains inside Glueprint
Everything below works with the Factory Droid 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 Factory Droid 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 Factory Droid 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 Factory Droid next to Claude Code, Codex, and the rest of the ACP fleet in the Command Center. The protocol differs; the surface doesn't.
Factory Droid 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 Factory Droid 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.
Factory Droid + Glueprint, asked plainly
Can I run Factory Droid with Glueprint?
Yes. Factory Droid is registered in the official Agent Client Protocol registry, and Glueprint implements the protocol's client side. It spawns the Factory Droid 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 Factory Droid subscription or API key?
No. Glueprint doesn't resell model access. Factory Droid 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 Factory Droid 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 Factory Droid sessions live, lets you send follow-ups, and handles permission approvals from anywhere.
Can I run Factory Droid 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.