colonizer-agentd 0.1.2

Daemon inside every Colonizer microVM: agent runner bridge, event log, terminals
colonizer-agentd-0.1.2 is not a library.

colonizer-agentd

The daemon inside every Colonizer colony.

A colony is a KVM microVM with a git worktree and a coding agent. colonizer-agentd is what the mothership (colonizer-harness) talks to in there. It runs the agent module, keeps the colony's event log and serves its terminal. Colonizer builds it as a static musl binary and mounts it read-only into every colony, whatever the image, so there is nothing to install by hand.

What it does

  • Bridges the agent. It starts the agent module and speaks its runner contract: commands as JSON Lines on stdin, events as JSON Lines on stdout.
  • Keeps the event log. It numbers each event, appends it to /var/lib/colonizer/events.jsonl and broadcasts it, so the mothership can reconnect and replay from any point.
  • Serves the terminal. A login shell in /workspace over a WebSocket PTY.
  • Answers only the mothership. It listens on port 7070 in the colony, and every request needs the colony's own bearer token, even inside the private mesh.
Endpoint What it does
GET /v1/health Version and the agent's state
GET /v1/events?since=<seq> WebSocket: every event after seq, then live ones; commands go the other way
GET /v1/pty?cols=<n>&rows=<n> WebSocket: a shell in /workspace
POST /v1/shutdown Shuts the agent down

The full contract is in the protocol.

Install

curl -fsSL https://colonizer.dev/install.sh | sh

That installs Colonizer, with this daemon built for the colonies' architecture. The install guide covers building from source. Code, issues and releases: Colonizer-dev/harness.

MIT.