#Status: what is done, and what is not
This page is rendered at build time from docs/status.md, so it cannot drift from the repository it describes: CI rebuilds it on every change, and a stale or unreadable source fails the build. It is the short, honest version of what is not ready yet.
#Released lately
What used to be listed on the home page as coming has shipped. Each item names the release it is in (the changelog):
- Observability, v0.2.7. Logs and metrics over OTLP to Grafana Cloud, Datadog, Honeycomb or your own collector, one trace per colony, and a Prometheus
/metricsendpoint. Off until you switch it on; no prompts, tool output, paths or commands are sent (/docs/observability). - A decisions inbox, v0.2.7. Issues waiting on your call and pull requests that need a person, as cards in the Inbox.
- Switch models from the top bar, v0.2.7, with what is left on each plan in use and saved model profiles.
- Pairing a phone by code alone, v0.2.7. A phone pairs with the remote link by the six-digit code, with no GitHub sign-in; the relay carries it since its redeploy on 2026-10-06 (below).
- Your cockpit, on your phone. The installable cockpit and web push since v0.1.10, pairing a phone from a QR code since v0.1.11, and the "Your cockpit" card with the address to bookmark since v0.2.3 (v0.2.2 carried it first but was tagged and never published).
- Fleets, v0.1.11, with the fleet colony list and one network policy for every member since v0.2.1 (v0.2.0 was tagged and never published) (/fleets).
What is merged on the harness's main for the next release is in its pending changelog.
#Open audit findings
The v0.1.3 audit (17 September 2026) verdict, not re-run on later releases (current: v0.2.22, 23 October 2026): not ready for unattended work on sensitive repositories, real credentials included (the audit). It found four ways a colony could cross into the host, filed as draft security advisories, and the audit page still lists all four as withheld until fixed. Unattended work waits on the audit's four checkpoints, G1 boundaries through G4 release, and "nothing is checked off yet, and no gate is cleared."
The checkpoints and what each one closes: /docs/audit.
#Remote access: the fixes are released, and the relay is redeployed
Remote access is off by default. The relay is deployed at my.colonizer.dev. Every finding of the security review, R1 to R5, is fixed in v0.2.7, as is pairing a phone with the link by the six-digit code alone, with no GitHub sign-in. The relay carries its half of both since it was redeployed on 2026-10-06 (the tunnel contract, the review).
Read it at /docs/remote-tunnel.
#There is no resolved rate yet
There is no published colony or issue resolved rate. The benchmark measures resolved and clean-resolved rates per run, and those numbers belong to that run: they are not a site-wide success rate, and no such number is promised or imminent (the bench).
#Not for unattended sensitive work
Run a colony attended: you launch it, you watch it, and a person reads the pull request before anything happens next (the audit). A repository with real credentials, or work that has to run with no reader in the loop, is out of scope until the audit's gates clear (the gaps page).
Start with /docs/audit.