Kilo, inside Glueprint.
The open source coding agent. Glueprint runs Kilo over the Agent Client Protocol it already speaks — adding live sessions on every device, approvals from your phone, parallel worktrees, schedules, and memory.
Kilo
Kilo Code
- Agent
- Kilo
- Maintainer
- Kilo Code
- Connection
- Agent Client Protocol
- Wire format
- JSON-RPC 2.0 over stdio
- Registry version
- 7.4.1
- License
- MIT
What is Kilo?
Kilo Code is an open-source AI coding agent built by Kilo Code, Inc. in Amsterdam and released under the Apache-2.0 license. It runs across VS Code and VS Code-like editors, JetBrains IDEs, a CLI, the cloud, Slack, and GitHub, and ships five modes: Code, Architect, Debug, Ask, and Custom. It supports 500-plus models with bring-your-own-key, local models, auto model routing by task and budget tier, and states zero inference markup.
- Apache-2.0, made in Amsterdam
- Five modes: Code, Architect, Debug, Ask, Custom
- 500-plus models with bring-your-own-key
- Auto model routing by task and budget
- Runs in editors, CLI, cloud, Slack, GitHub
Best for Teams wanting one open agent across many editors and surfaces with flexible model choice.
Sourced from Kilo's official site and repository.
How Glueprint runs Kilo
Kilo connects over the open Agent Client Protocol — one generic adapter implements the protocol's client side, so Kilo gets the same surfaces as every other harness:
Glueprint spawns Kilo, not a fork
Glueprint finds the Kilo 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 Kilo 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 Kilo 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 Kilo 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 Kilo gains inside Glueprint
Everything below works with the Kilo 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 Kilo 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 Kilo 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 Kilo next to Claude Code, Codex, and the rest of the ACP fleet in the Command Center. The protocol differs; the surface doesn't.
Kilo 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 Kilo 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.
Kilo + Glueprint, asked plainly
Can I run Kilo with Glueprint?
Yes. Kilo is registered in the official Agent Client Protocol registry, and Glueprint implements the protocol's client side. It spawns the Kilo 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 Kilo subscription or API key?
No. Glueprint doesn't resell model access. Kilo 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 Kilo 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 Kilo sessions live, lets you send follow-ups, and handles permission approvals from anywhere.
Can I run Kilo 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.