#Colonizer protocol v1

Three hops, one event vocabulary:

agent runner ──stdio JSONL──▶ colonizer-agentd ──WS (mesh)──▶ colonizer ──WS──▶ browser

All messages are single-line JSON objects with a type field. Unknown types and unknown fields must be ignored (forward compatibility).

Model calls take a path of their own, outside these hops: a routed <provider>/<model> goes from the colony through the mothership's provider gateway (§6.5), which holds the provider keys, and an unrouted model goes from the colony straight to the API its agent module's manifest names (egress.api in module.json: api.anthropic.com for Claude Code, api.openai.com for Codex).

#Areas

The protocol, one file per area. Each area file opens with its own title and links back here.

Generated by node scripts/doc-index.mjs write: add a file under docs/protocol/ and rerun; don't edit by hand. <!-- doc-index:start -->

• Activity log
• 3. colonizer-agentd API (VM, port 7070)
• Accounts, tokens and install settings
• Autonomous and burn-down modes
• Decisions inbox
• Duplicate-colony prevention and issue claims
• 6.6 Findings
• 6.11 Fleet export bundle (#687)
• Fleet: hosts, pairing, history and member health
• 4. Harness API (browser)
• Updates, downloads and telemetry
• Loops
• 6.2 Shared memory (runner ⇄ mothership)
• Model routing, tiers and the second opinion
• 6.3 Mothership API additions
• Observability: GET /metrics
• Plugin directories
• Pre-flight scan
• 6.5 Provider gateway (v1.2, issue #5)
• 6.7 Red-team runs
• 6.10 Remote access (tunnel)
• 2. Agent runner contract (module ⇄ agentd, stdio JSON Lines)
• Saved secrets: /api/secrets
• Sessions: events, transcript and terminal
• Spend and cost history
• Token savings
• 7. Standard names (UHP)
• 1. Files inside the VM
• Web UI
• Webhooks

<!-- doc-index:end -->

#Where the old sections went

Every heading of the single-page protocol, in its original order, and the area file it moved to: