v2.0.2-main.2

breakaway v2.0.2-main.2

Board

• Predict a task's footprint: paths it names, files tasks like it changed, shared files, and overlap (BRK-317, #495)
• Keep the files each pull request touches (BRK-316, #496)
• Footprints and path claims in the store, the CLI, and the API (BRK-318, #497)
• Give back an agent's task claim after an hour of silence with no pull request (BRK-321, #498)
• Claim at the edit, and tell the riders who touches what (BRK-320, #499)
• Every starter schedules by footprints (BRK-319, #500)

Web

• Show footprints on the board (WEB-130, #501)

Docs

• Document footprints in the manual and the site's docs (DOC-49, #502)

v2.0.2-main.1

breakaway v2.0.2-main.1

Board

• Tell running chases' agents what to do when GitHub is down (BRK-279, #479)
• Each peloton post reaches an agent once, and listening returns sooner (BRK-278, #480)
• Watch Claude's status page and hold chases while it's down (BRK-315, #481)
• Make the road captain a role on the board (BRK-275, #482)
• Hold a chase at its review cap until the owner merges (BRK-276, #483)
• Write the owner an hourly digest of a chase (BRK-277, #484)
• Agents close their open questions before they leave (BRK-281, #485)
• Review risky paths with a separate agent before Merge when green (BRK-280, #486)
• Keep the owner's words on a task, quoted, for every agent that picks it up (BRK-284, #487)
• Facts about platforms carry their source (BRK-282, #488)
• Adding a task shows similar open tasks first (BRK-283, #489)
• Say on the console when the next deploy would undo a Worker setting (BRK-313, #490)
• Retire the first install's shipped backfill from the Worker (BRK-98, #492)
• Name Cloudflare's Workers Editor role for self-update's token (BRK-244, #493)
• Restore a board from an export into an empty board (BRK-234, #494)

Other

• Shape footprints, so agents are scheduled by the files each task touches (IDEA-55, #491)

v2.0.1

breakaway v2.0.1

Docs

• Give Architect a full docs section on the site (DOC-48, #478)

v2.0.1-main.1

breakaway v2.0.1-main.1

Docs

• Give Architect a full docs section on the site (DOC-48, #478)

v2.0.0

breakaway v2.0.0

breakaway 2.0.0 runs the infrastructure too, and you still decide. With Architect, agents propose changes to what your repositories run on by pull request, the plan waits for you on the board, and your repository's own apply workflow applies it. And from 2.0.0, breakaway is free for personal and noncommercial use, under the PolyForm Noncommercial License 1.0.0.

Architect

• Connect a provider on Connections: Cloudflare, with a read-only token. A checklist on each repository's card links to Cloudflare's token page with the permissions filled in, and shows, per environment, whether its GitHub environment is ready: it exists, only the default branch may deploy, and it holds the write token. The write token lives there, never on the board. With no provider connected, Architect stays off and makes no call.
• Infrastructure is a new view (g then n): each repository's environments, their health, cost, and freeze, and the platform's alerts. A repository on the deploy flow gets staging and production by itself, with its deploys, Promote, and Roll back recorded on them.
• Each environment is a console: a map of what runs and how it's bound, a live stream of its signals, its plans, incidents, drift, what nobody owns, and recent deploys. What the desired state declares stays on the map until the inventory sees it.
• Desired state lives in the repository, in .github/breakaway-infra/<environment>.json. Nobody has to write the first one: Describe it as code drafts it from what runs, and npx breakaway infra adopt writes it into a checkout.
• Plan from the board. On the console, change a setting, add a resource from a template, or remove one, and watch the plan form as you edit. Propose the change, and the board opens its pull request, with the apply workflow in it when the repository doesn't have one yet. Approve merges it and applies it. You can also build an environment from nothing, or have an agent set one up in a short wizard.
• Every plan says what changes, what it costs, what else it touches, and whether it can be undone, and it shows as a check on its pull request. The policy decides which plans wait for you, per repository and per environment, and you change it in place on its own page; loosening it is never one press.
• Approve and Reject are yours, on the board, like Merge. The repository's apply workflow applies an approved plan under the environment's lock, checks its health, and rolls back if it fails. A run that failed before applying anything can be started again, and an applied plan looks at the environment again at once.
• Envelopes are bounds you approve once on an environment, like "2 to 10 instances" or "3 restarts a day". Inside one, the board scales and restarts without asking you again. They start empty, so until you set one, every scale and restart waits for you.
• Signals and incidents. Health, the platform's alerts, and cost are signals. One that crosses a rule opens an incident, a task tagged +incident in the repository that owns what broke, with its steps: diagnose, propose, approve, apply, verify. An agent diagnoses it only when you start one, or from a runbook you turned on. Routines can start on signals, on infrastructure events, and on new issues.
• Drift shows what runs that no longer matches the desired state. Mark as break-glass records a change you made by hand and adds a task to put it in code; the board never undoes it.
• Cost is an estimate per resource, added up by environment, repository, and task, with a budget per environment and a signal near it and over it. Pick your currency in Settings.
• Short-lived environments: one per task when a repository asks for it, removed when the task closes.
• Freeze stops every plan on an environment. Freezing a pipeline's production is the deploy pause too: the board sets DEPLOYS_PAUSED, and Roll back still works.
• Agents work infrastructure the way they work code, and neither they nor the board hold write credentials: npx breakaway infra and the MCP server read environments, plans, signals, and incidents; infra check and infra add write a change for a pull request. Agents never apply or approve.
• The board's own install is observe only: Architect watches it and never changes it.

The licence

• From 2.0.0, breakaway's licence is the PolyForm Noncommercial License 1.0.0. It's free for personal and noncommercial use: use it, change it, and self-host it. Commercial use is by exception, granted free and case by case. LICENSING.md says it in plain words, and how to ask.
• Releases before 2.0.0 stay under FSL-1.1-Apache-2.0.
• Contributions now come with a contributor licence agreement, signed on the pull request.

On the board

• The roadmap is a timeline: each feature from its first work to when the board's pace says it's likely done. Give a feature a planned start and end, drag its bar, and see whether the pace agrees. Agents can plan the roadmap too, and every change they make shows in Activity with an undo.
• Feature pages open on an overview, with the full task list a step away. The graph folds done work and shows the path to the last task.
• Code in diffs is highlighted, and Markdown and text files preview as a rendered diff.
• Build a pre-release from a repository's release flow on the board, and see when main is ahead of the latest one.
• The board spends less of GitHub's rate limits, shows what's left per repository on Connections, and paces a busy repository's sync by the budget left.
• Pings no longer have a count per task, and a proposal no longer has a count of changes, only its size.
• Settings and Connections are laid out across the width, the peloton's posts can be resized, and scrollbars follow the theme.

Updating

Nothing by hand: update and deploy as usual. There's no new binding, Durable Object class, migration, route, or cron, and Architect stays off until you connect a provider. Updating to 2.0.0 says what changes by itself, what your repositories get, and how to go back to 1.5.3.

• Accept the GitHub App's new permissions when you want what they're for: Checks (a plan's check on its pull request), Variables (freezing production sets DEPLOYS_PAUSED), and Issues with its event (routines on new issues). Workflows, Administration, and Environments are optional too: they let the board's change bring the apply workflow, make GitHub environments for you, and check a write token's name. The board works without each, and says what's waiting.
• To apply in a repository, give it a GitHub environment per environment, limited to the default branch, holding that environment's write token; the repository variable BREAKAWAY_URL; and the apply workflow, from npx breakaway infra init or the board's change. Get started with Architect walks through it.
• Run npx breakaway repos init <slug> --update in each repository and merge the result, so its agents get the new core, tasks skill, and CLI.
• If you ran infra init on a 2.0.0 pre-release, run npx breakaway infra init --update there and merge the result.

---

Board

• Mark its spec approved (BRK-223, #310)
• Set the version to 2.0.0 (BRK-231, #312)
• Add Architect's append-only audit trail (BRK-175, #315)
• Add Architect's provider interface, its registry, and a fake provider for tests (BRK-173, #316)
• Spec pluggable agent providers with pooled capacity, next to Claude (BRK-176, #317)
• Add environments, with a freeze switch and the board's own install always observe only (BRK-174, #318)
• Add Architect's signals stream, redacted and kept for a set time (BRK-190, #319)
• Write down the first provider's API surface and narrowest tokens (BRK-188, #320)
• Connect providers' read-only tokens on Connections (BRK-194, #322)
• Add Architect's inventory, with scope, relations, ownership, health, and cost (BRK-177, #323)
• Read each environment's desired state from its repository, and check it (BRK-180, #324)
• Add environment locks, one apply at a time, with expiry and the owner's release (BRK-179, #325)
• Discover what a Cloudflare environment runs into the inventory (BRK-189, #328)
• Make adding, changing, and removing an environment cookie-only (BRK-233, #330)
• Drop the stale note on the freeze audit (BRK-232, #331)
• Keep plans with their cost change, blast radius, and whether they can be undone (BRK-178, #332)
• Estimate each Cloudflare resource's monthly cost from its usage (BRK-193, #335)
• Start routines on signals, with allowlisted fields, deduplicated and capped (BRK-196, #336)
• Send the deploy flow's failed deploys and roll backs to the signal stream (BRK-198, #337)
• Observe Cloudflare health and send its alerts as signals (BRK-191, #338)
• Compare each environment with its desired state on the cron, and draft one plan for its drift (BRK-184, #339)
• Check every plan against the repository's policy, with the default policy (BRK-181, #342)
• Plan and apply Cloudflare Workers and their bindings (BRK-192, #344)
• Open an incident task from a signal that needs action, with its steps (BRK-197, #345)
• Make a pipeline's staging and production environments, and record its deploys on them (BRK-195, #346)
• Read Architect's environments, inventory, plans, signals, and incidents over MCP (BRK-202, #347)
• Start routines when an issue is opened or reopened (BRK-237, #349)
• Mark drift as break-glass, record it once, and make a task to put it into code (BRK-187, #350)
• Approve or reject a plan, owner-only and cookie-only, with a push (BRK-182, #352)
• Show an infrastructure change's plan and policy results as a check on its pull request (BRK-185, #353)
• Show costs in your currency, at a rate you set (BRK-226, #354)
• Make freezing p...

v2.0.0-main.121

breakaway v2.0.0-main.121

Board

• Move the plugin, the session hooks, and repos init to breakaway@2 (BRK-312, #477)

Docs

• Prepare the 2.0.0 stable: release notes, spec statuses, and the docs, site, and launch copy against what shipped (DOC-41, #476)

Brand

• Move Architect's claims into the brand guide's list for 2.0.0 (ID-7, #475)

v2.0.0-main.120

breakaway v2.0.0-main.120

Board

• The board's change brings the apply workflow, and says so before Approve when it can't (BRK-307, #468)
• An environment with no target plans with the one Worker its merged desired state declares (BRK-309, #469)
• An applied or rolled-back plan refreshes its environment's inventory and drift at once, and again shortly after (BRK-310, #471)
• Keep a change's number when the apply workflow is refused (BRK-311, #472)
• A plan's run that failed before applying anything can be started again from the board (BRK-308, #473)

Web

• The policy page lists the default and each environment as sections you change in place (WEB-128, #467)
• Keep what the desired state declares on the map until the inventory sees it (WEB-129, #470)

Launch

• Refresh the homepage's road ahead from the board's roadmap (LCH-41, #474)

v2.0.0-main.119

breakaway v2.0.0-main.119

Board

• A contributor licence agreement, checked on pull requests (BRK-296, #448)
• Switch breakaway's licence to PolyForm Noncommercial 1.0.0 (BRK-295, #449)
• Start routines on infrastructure events (BRK-293, #450)
• Plan a from-nothing environment's pull request with the target its change gives it (BRK-298, #455)
• Guide the owner through the read token and each environment's write token (BRK-304, #460)
• Sync a repository whose checks run each minute, paced by the budget left (BRK-272, #463)
• Sign the CLA with a signed copy, the sign phrase, and the owner's countersign (BRK-306, #465)
• The kickoff agent can include the first infrastructure plan (BRK-305, #466)

Web

• A policy manager on the infrastructure console (WEB-123, #451)
• Pick infrastructure triggers on a routine's form, and see which event started a run (WEB-122, #454)
• Word a plan an envelope approves as inside its envelope, never waiting for you (WEB-125, #458)
• Re-render 2.0.0's film so shot 11 no longer says waiting for you (WEB-125, #459)
• Lay out Settings across the width (WEB-127, #461)
• Kickoff's last step is Run it: required, with Not needed as a choice (WEB-126, #462)

Docs

• A licensing page on the site, and a form to ask for an exception (DOC-43, #453)
• Offer a private way to ask for a licence exception, by email (DOC-45, #457)
• A licence exception agreement template, and the licensing pages saying exceptions are granted by a signed agreement (DOC-47, #464)

Launch

• 2.0.0's launch copy and film follow the new licence (LCH-40, #456)

Brand

• The brand guide's licence words for PolyForm Noncommercial (ID-8, #452)

v2.0.0-main.118

breakaway v2.0.0-main.118

Board

• The console reads what a Worker's bindings already bind (BRK-285, #438)
• Approve never dead-ends, and a change that plans nothing offers Merge (BRK-286, #440)
• Build an environment from nothing on the console (BRK-291, #443)
• Plan a new environment's route or custom domain before its Worker runs (BRK-292, #444)

Web

• The Plans panel shows the console's change, the plan applying, and recent plans (WEB-115, #439)
• The feature page opens on an overview, with the full task list a step away (WEB-118, #442)
• Say plainly when a new environment's first apply fails (WEB-120, #445)
• Have an agent set up a new environment in a short wizard (WEB-121, #446)
• Resources a change adds open in Change like any other (WEB-119, #447)

Launch

• Make 2.0.0's film from the real board at three scales (LCH-38, #441)

v2.0.0-main.99

breakaway v2.0.0-main.99

Board

• Approving a change the board proposed merges its pull request and applies it (BRK-260, #413)