Repository navigation
Factory 0.3.0
Factory 0.3.0 adds tracks and an Explorer, so a task can be tried before anyone builds it. It also lets you compare Health before and after a change, and counts only the latest run of each CI check.
Tracks
Each task gets a track that decides its path before the production line:
- direct: a small, explicit change, straight to a Builder.
- plan: the Planner's READY plan comes first. No Builder starts until it's marked ready.
- explore: a time-boxed Explorer tries it first, with no PR. Then you decide what comes next, and the Lead records it by changing the track.
The Lead picks a task's track with bb factory track APP-12 direct|plan|explore when it takes the task, and you can change it, including from the task on the Factory page. Assigning the Planner or an Explorer moves a task to that track, and a Builder on a task with no track makes it direct.
Explorer
- Its own worktree, a 45-minute time box and no PR. Start it with
bb factory assign APP-12 --role explore. - A required report. It ends with a task comment recorded by
bb factory explore-report: hypothesis, what was tried, what was learned, a recommendation (build, plan, explore more or close) and what wasn't checked. - The time box. The factory reminds the Explorer near its end, tells the Lead once if it runs past, and gives up on one that stops without a report after twice its time box.
- Clean-up. Once it has finished, the factory archives its thread and deletes its worktree and local branch. The host worker deletes only a branch named as that Explorer's, never one still checked out.
- Several candidates. To compare approaches, ask for up to 3:
--candidates 2with one numbered approach each in--instructions. Once all have finished, the Lead gets them side by side, and the task on the Factory page shows them in columns.
Planner and Designer
- The Planner can end with NEEDS SPIKE, which moves the task to explore, or RECOMMEND CLOSE. That, like an Explorer's close recommendation, marks the card "Close advised". Only you close a task on an agent's advice.
- The Designer proposes two or more approaches, with their trade-offs, when the choice is open.
Health and CI
- Health for a date window.
bb factory health APP --since 2026-11-05and--before 2026-11-05count only PRs opened in that window, to compare before and after a change. The Health view on the Factory page has the same two date fields. - The latest run of each check. When a check ran more than once on a PR's head, only its latest run counts, as on GitHub. A run cancelled by a newer one no longer holds the merge card.
When you upgrade
- Tracks are on for new factories. Existing factories keep working as before, including the old plan gate, until you turn them on from outside an agent thread:
bb factory tracks APP on. - The Planner's gate stays. When you turn tracks on, a task that already has a Planner counts as plan, so no Builder starts before its plan is READY.
- The Agents settings gain an Explorer seat, on Claude Code by default.
- Leads already running see tracks through their standing rules and the skill, not their first brief.
- The host worker can now delete Explorer branches, besides running its
gh prcommands.
Limits
- The time box is a reminder and a notice to the Lead, not a hard stop.
- Closing a task on an agent's advice is yours by rule. The factory doesn't enforce it.
- The Factory page starts one Explorer. Several candidates need the CLI or the Lead.
- Pushed branches: an Explorer is told never to push. A branch it pushed anyway stays on GitHub.
- Tried on real tasks: each track on the sandbox, including a 2-candidate explore that the Lead got side by side, with both worktrees and branches cleaned up afterwards. Not yet: the time-box reminder, the past-the-time-box notice, NEEDS SPIKE, RECOMMEND CLOSE, and choosing a track on the page.
Full Changelog: v0.2.1...v0.3.0