What shipped.

Every in-flight issue now carries a current_status field: a human-readable description of what the pipeline last did, written atomically alongside every state transition. Analyzer, Planner, Developer, Reviewer, Merger, and Sweep each emit a status string at key moments in their execution; operator actions and system events (cost-cap hits, auto-unblocks, dependency resolution) do the same. The status surfaces in the SDK via getIssueStatus() and getIssueEvents(), and in the dashboard IssueDetail view. Issue #3977.

Also shipped this week: the CI repair executor. When a build fails and the failure is diagnosable, the pipeline now re-invokes the Developer with the structured CI failure context instead of escalating to the operator. Issue #3913.

The Colony Cloud dashboard now receives pipeline events over a server-sent events stream instead of polling on a fixed interval. Worker status updates, cost changes, issue state transitions, and alert events push to the browser as they happen. A useSSE hook wraps the stream with automatic reconnect and a polling fallback when the connection is unavailable. A connection indicator in the header shows stream health; the HiveView breathing dot now dims when data is stale rather than just when the connection drops.

IssueDetail shipped a parallel set of improvements: the header bar now surfaces the linked PR, current cost, and relative merge time at a glance. A PipelineRail component renders the issue’s phase history visually, and the view auto-refreshes while an issue is in flight.

The colony CLI now ships bootstrap templates for Rails, Next.js, and Django, each with integration flags (Stripe, Resend, R2) that scaffold a working app the pipeline can operate against from issue one. End-to-end smoke tests cover all five bootstrap templates in CI. PRs #3650, #3651, #3653.

The home page now leads with the category sentence: The orchestration layer for AI coding agents. The receipts band — 1,284 PRs merged, 14m median cycle, $0.91 per merged PR — moved above the problem framing. The primary CTA is Read the receipts →, pointing at the new /built-by-colony/ destination (live data once the public-stats API ships).

Tightened the cost-cap escalation path so that builders spawning subagents bubble their incremental spend up to the parent issue’s budget in real time, instead of at task close. Inspector now sees the spend trajectory and can escalate to operator before the cap is breached. PR #2843.

Hybrid tenancy — control plane managed by Colony, worker pools in your VPC — is now in private preview with a small set of design partners. Public preview Q3 2026. Talk to us on the pilot call if you need stricter data residency than Cloud’s regional default provides.

colony why <issue> now emits a structured diagnostic report for any issue, paired with a new dead-letter table that captures terminal failures with block_reason and block_context so the Sentinel agent surfaces them to operators instead of letting them sit silent. PRs #2459, #2488.

Colony now talks to Anthropic models through Azure AI Foundry, for teams whose enterprise procurement already covers Azure model contracts. The worker config picks the provider per agent; the cost ledger reports through the same pass-through pricing. PR #2154.

Between March 31 and April 1, the pipeline merged 120+ PRs on its own repo in a single 36-hour window — Mayor through Marshal, with Inspector running deterministic checks and an LLM review before every merge. The failure modes the session surfaced are now encoded as recovery logic in docs/production-learnings.md and anchor the proof points the rest of the site leans on.

Several large internal modules — the Builder executor (2,547 lines), the Mayor’s coordination logic, the SDK type surface — were decomposed into focused submodules through self-improvement issues the pipeline filed against itself. Surveyor prompts now require call-site verification before concluding an issue has no work to do. PRs #1357, #1408.