Skip to content

Colony Cloud Changelog

Release notes for Colony Cloud — the managed product layer including the commercial dashboard, Service API, Worker infrastructure, billing, and onboarding.

Colony Cloud ships in monthly releases named by month, such as cloud-v2026.11.0, with occasional fix releases (cloud-v2026.11.1). From the first versioned release on, this page has one section per release, newest first. Each section names the Colony release it bundles and repeats the Colony changes that need your attention: anything breaking, deprecated or changed in behavior, migrations, and security fixes. Before each release you get an email with what is coming and when.


Released 2026-11-12. Bundles Colony v0.3.0.

The first versioned release. It is the release candidate that has run in production since 2 November, so if you were already on it, nothing changed on release day and you don’t need to do anything.

  • The Mayor is a docked panel. It stays open as you move around the dashboard, keeps your conversations (visible only to you, deleted 30 days after the last message), knows the page you’re on, searches Colony’s docs, and renders Markdown replies. Work items and faults have Ask the Mayor about this. An organization can route the Mayor through its own model access instead of Colony’s. See Colony Mayor.
  • Accept an epic. Accept on an epic waiting for review merges its branch, with its subtasks, once checks pass. It counts as the approval, so no code-host review or account is needed unless your repository’s own rules require one. The Mayor and the hosted MCP’s colony_act can do the same.
  • The patience ladder. If an ask, a manual block or an unacknowledged fault goes unanswered for long enough (4 hours, 2 hours and 30 minutes by default, set on Operations › Settings), Colony tells the next person. Work items and faults show who has been told.
  • Work counts what you owe. Items Colony has flagged for a person count as owed in Your queue and the Work count, whatever their state, and you answer a question, pick or dependency decision in the row.
  • Per-repository settings. A repository can set its own required CI checks, CI timeout and base branch, and hold its own env secrets (Repository secrets). Merge method (merge commit, squash or rebase) is on the Merging settings.
  • The hosted MCP. When you connect a client you choose which organization it’s bound to, and the server says which one it is. colony_repos lists your repositories, and colony_work status and list cover a whole tenant without naming a repository. See MCP & Editor Integration.
  • Customer-owned Pipeline Stores can connect through Cloudflare Hyperdrive (Colony sets it up), or through Cloudflare Tunnel with no inbound port opened.
  • Claude subscriptions are no longer available for agents. Agents sign in with an Anthropic API key. A repository still set to a Claude subscription shows a warning asking you to switch.
  • Mayor limits. The Mayor runs on Claude Haiku 5.5 with a monthly cap per plan (Team $20, Business $80, Enterprise $400) and a daily limit per person of 10% of that. It pauses while a subscription is past due or canceled.
  • CI check timeout. review.ci_check_timeout can be at most 86400 seconds (one day).
  • Organizations. Only Colony staff create new organizations, and an Admin can no longer invite or remove an Owner.
  • Markdown tables, strikethrough, task lists and links render in work items and comments, not only in the Mayor.
  • Mayor routing is set on the tenant’s Operations › Settings; a repository’s settings show it read-only.
  • Sign-in. Magic links survive mail security scanners: the link opens a confirmation page and is used only when you press Sign in, and links stay valid for 60 minutes. Accounts with no linked GitHub account see a Connect GitHub banner.
  • Settings. A save that committed no longer reports an error when a follow-up step fails; you get a warning instead. The tenant settings page no longer overwrites stored settings after a failed load.
  • Default steward shows correctly in Account › Tenants and can be changed.
  • Worker images pull with Docker’s containerd image store, and each host pulls its own architecture.
  • Self-improvement tracks keep their selection mode on Cloud workers, so a track whose label isn’t <prefix>:si-… offers its options menu again.
  • colony:active no longer toggles every few minutes on epics waiting for subtasks.

From Colony v0.3.0:

  • Slash commands and clarification replies need write access to the repository by default. A reply from someone without it, such as the reporter of an externally filed issue, no longer resumes an item waiting for clarification. Set commands.authorization to any to allow anyone.
  • Formatting runs only when you configure it. Colony no longer detects a formatter. A repository that relied on one should set review.format_command.
  • Repository intelligence is always on. Agents’ prompts grow by up to intelligence.retrieval.token_budget tokens (1,200 by default); lower it to cap the cost.
  • Stale detection now works. The first sweep after the upgrade marks every item already past its threshold colony:stale and comments once on each.
  • MCP inputs removed: pr_number (use change_number) and label on colony_work, pr_number on colony_review, and labels on colony_file_issue (use as_epic).

Colony’s other breaking changes in v0.3.0 (Postgres certificate verification, removed configuration keys, the repository clone path) apply to self-hosted deployments. On Cloud, Colony made them for you.


The changes below predate versioned releases, and are dated by the week they became available in production.


  • Autonomy › Strategy now leads with the Strategist’s proposal when one is waiting: goals with how the charter is doing, what changes in the strategy pool against the tracks running now, the capacity split, and what the Strategist read. Every change cites its sources, and the proposal says it can be wrong.
  • You can Approve and apply, Decline with a required reason, or edit, then approve. Approving applies the proposal at once; there is no separate approved step. History shows the trigger, the decider and the reason for each version, and Revert applies the previous version’s tracks again.
  • Strategy reviews count as work you owe: Autonomy in the rail and the Strategy tab show how many repositories have a proposal waiting. strategy.proposed and strategy.applied are new webhook events.
  • The charter is now an ordered list of goals with an optional “Done when”, at /autonomy/strategy/charter.
  • Strategy settings on Autonomy › Settings set approval (a person, or automatic), capacity share, selection and the cooldown floor. Colony’s own scheduler is the only one now, so the weekly “Automatic weekly proposals” toggle is gone.
  • Strategy tracks show their owner in Tracks. Their prompt, share, cadence and menu mix are held by the strategy; the cooldown floor and selection mode stay yours.
  • You can now delete a stored credential from Secrets & keys. Workers no longer receive it. Deleting needs the tenant-administrator grant, and the two Pipeline Store keys can’t be deleted.
  • Credentials saved for a Claude provider you no longer use stay visible with the note “Not used by the current Claude provider”, so you can find and remove them.
  • The standalone /drafts editor is gone (the old URL redirects to the Ledger). You now create a proposal with New proposal in the Intake band of the Ledger.
  • You refine a proposal in its intake sheet at /work?proposal=:id. Authorize files it as a GitHub issue and enqueues it. See Drafts.
  • Old /drafts links now redirect to the Ledger, and /drafts/:id links redirect to that proposal’s intake sheet.

The following pages were added to the Colony Cloud pillar after the June documentation release:

  • Drafts — write issue ideas as proposals, refine them, and authorize them into the pipeline as GitHub issues.
  • Digest Notifications — configure scheduled digest emails and Slack summaries for pipeline activity (since replaced by Report delivery, where each person subscribes to day, week or month sealed reports on the Reporting home).
  • Outbound Webhooks — register webhook endpoints and manage delivery logs for real-time pipeline events.
  • REST API & API Tokens — generate personal and org-scoped API tokens and browse the Colony Cloud REST API reference (personal and org-scoped tokens since replaced by connections).
  • Operator Assistant — in-dashboard conversational AI for pipeline management, available on Team, Business, and Enterprise plans.

Per-repository deep-dive pages are now available under each connected repository:

  • Current Status — live pipeline state, open issues, and health signals for the repository (since folded into the Ledger).
  • Findings — aggregate intelligence findings surfaced by Colony’s analysis passes (since removed).
  • Intelligence — codebase understanding snapshots and context Colony has built for the repository.
  • Retrospectives — per-issue retrospective records with planned-vs-actual file set comparisons.
  • SI Tracks — view and manage self-improvement tracks configured for the repository.
  • Strategy — Strategist-proposed strategy snapshots, charters, and approval workflow.
  • Workflow — the active workflow definition driving the repository’s pipeline execution.

The Settings area now includes dedicated pages for each configuration domain:

  • Account — your display name, how you’re notified (with a notification log), password and linked sign-in accounts, and the prerequisites for connecting a GitHub organization.
  • Organization — organization name, slug, and permanent deletion (members since moved to Team & Roles; plan and billing since moved to Billing).
  • VCS Connections — GitHub App installations and repository access grants (labeled Repos & access in the sidebar).
  • Workflows — org-level browser of registered workflow versions, with state-machine detail and grant-gated authoring controls.
  • Agents — org-level pipeline and agent defaults that apply to all repos unless overridden (worker registration and tokens are documented on Workers).
  • Model Routing — route each task type to a model by complexity tier, with a global override.

Two new pages consolidate all cost and budget information in one place:

  • Cost & Budget — Cloud reporting page covering cost summary horizons (24h/7d/30d/lifetime), cost timeseries with granularity and bucket limits, model spend share and efficiency signals (max-turns, no-progress), budget overview (per-repo budget_cap_usd caps, burn rate, and projected exhaustion), monthly cost projection with P25/P75 bands, and the per-issue estimate feature.
  • Cost & Budget — Product-neutral concept page explaining how spend is measured, what budget caps mean, and the assumptions and limits behind cost projections. Relevant to both Cloud and self-hosted deployments.

The Reference pillar of this docs site is now complete:

  • Glossary — definitions for every first-class Colony concept, with cross-links to Core Concepts.
  • Configuration Schema — flat field-by-field reference for all colony.config.yaml sections, all three tiers.
  • Pipeline States — every pipeline state, every valid transition, the canonical state machine diagram, and per-executor transition constraints.
  • Metrics — canonical definition, calculation method, and unit for every metric surfaced in the Colony Cloud dashboard.
  • Slash Commands — complete syntax reference for every operator slash command.
  • Changelog (this page) — release history for Colony OSS and Colony Cloud.

The Colony Cloud pillar documentation is now complete, covering every major product area: onboarding, connecting repositories, dashboards, team and roles, secrets, BYO Workers, migration, billing, security, troubleshooting, external PR review, self-improvement tracks, and MCP & editor integration.

Window boundaries are now consistent across all dashboards. Previously, different views could compute slightly different start and end times for the same window.


Colony Cloud release notes before June 2026 are not published. If you need details about a specific change, contact support.