Session modes
The team works in seven modes, in two groups. Deliverers ship merged code; you pick the cost-versus-assurance point per ticket. Producers keep the queue full so the Deliverers always have work to do.
Deliverers — output is a merged PR
Three agents split the work: one plans, one implements, and an independent reviewer gates the plan and the diff before merging. The highest-assurance path for changes that warrant it.
Two agents: one owns planning and implementation, the other reviews. The reviewer authored neither the plan nor the code, so the design still gets a genuine second pair of eyes — at a lighter cost than team.
A single agent owns the full cycle — plan, build, review, merge, and notify. The fastest, leanest path for small, low-risk changes.
Producers — keep the queue full
Open-ended investigation with no code to deliver. It turns a fuzzy idea into concrete, self-standing tickets that the Deliverers can pick up.
A quality auditor for the repo. It reviews merged work and files structured tickets about what it finds — it never writes delivery code itself.
Two peer agents deliberate a hard question — one proposes a position, the other stress-tests it — and converge on a concrete conclusion, resolving disagreements without escalating to you.
A bare single agent working in the current directory, with no queue and no PR workflow. The hands-on outlier for when you want to drive directly.
See the pipeline behind the modes
Every Deliverer runs the same underlying loop — plan, build, review, merge. Read how it works for the guardrails that keep autonomous merges honest.