Colonizer.dev

_{Harness  ·  Vision  ·  Architecture  ·  Protocol  ·  What it does not do}

Every issue gets a colony: a private microVM with a fresh worktree and a coding agent inside. Colonies stay linked to your machine over a private mesh, ask you questions as choices, and come home as pull requests.

Your machine is the mothership. It holds the credentials, and no colony ever does. The code is MIT.

This matters more than anything else on this page, so it is first.

Nothing beyond the harness is built. colonizer.dev is a name, not a product, and there is no price, published or estimated.

Two labels are used everywhere, and they govern the tense of the sentence around them:

• SHIPPING: merged, in a public repository, and exercised on a real machine.
• PLANNED: named, unspecified. Nothing written.

Real, from the mothership's log for one colony on 14 September 2026, before the repository moved to this organisation. Unedited.

13:19:38 cloning https://github.com/ParallelEntrepreneur/colonizer.git (first session for this repository)
13:19:40 fetching origin
13:19:41 creating worktree on branch colonizer/session-79fabc85 from origin/main
13:19:41 starting the private mesh
13:19:41 booting microVM colonizer-79fabc85 (node:24-bookworm, 4 vCPU, 8G)
13:19:41 waiting for the microVM to join the private mesh
13:19:44 colonizer-79fabc85 joined the mesh at 100.64.0.2
13:19:50 agent daemon is ready
13:19:50 connected to the agent

Twelve seconds from nothing to an agent in its own machine, on its own branch, one WireGuard hop away. Seven seconds later it asked its first question, as a card with two options.

1. A colony is a machine, not a container. Each task runs in a KVM microVM with its own kernel. The agent works without permission prompts, because there is nothing worth protecting on the other side of the wall.

2. Secrets stay home. The GitHub token never enters a colony. The agent's API credential is a placeholder, swapped in by a host-side TLS proxy for exactly one host. The mothership commits and opens the pull request after the colony is gone, and treats what the colony left behind as untrusted.

3. Every colony is one hop away. A private mesh (bundled Headscale and WireGuard) links each colony to the mothership, separate from any network you already use. Chat and a real terminal ride on it. Colonies can't reach each other.

4. Decisions, not prose. When an agent needs you, it asks with concrete choices and an "Other" answer. If it slips into a plain-text question, it is asked to try again as a card.

5. Everything is a module. Source, sandbox, mesh, agent, interfaces and publish are swappable providers behind small contracts. The agent contract is JSON Lines on stdio, so a module can be written in anything.

Stated here rather than buried, because trust is the whole point.

• One machine, Linux x86_64 with KVM. No macOS, no remote hosts yet.
• One agent, one forge. Claude Code and GitHub.
• No login on the web UI. It binds to loopback and should stay there.
• Not yet run end to end: opening a pull request from a colony, and the installed-app mode of the installer. Both are implemented.
• No CI, no releases, nothing on crates.io or npm.

The roadmap is the issue tracker. There is no private version of it.

github.com/Colonizer-dev/harness  ·  colonizer.dev

_{MIT license · Colonize your backlog.}