Night run

A night run hands a written spec to a crew of agents and lets them work while you sleep: a lead plans the slices, builders build them, a reviewer reads each one, a verifier proves it, and the lead writes a morning brief you read with your coffee.

Starting a run

1. Write the spec

   A PRD, a ticket, a paragraph — anything that says what done looks like. Paste it into the night-run sheet or point at a file in the repo.

2. Pick a crew

   Settings › Night run has built-in crews and lets you save your own: which provider plays lead, builder, reviewer and verifier. Mixing vendors is the point — a Claude lead, Codex builders, a Grok reviewer — so no single quota carries the night.

3. Set the guardrails

   • Review the plan first: wait for you to approve the lead's plan before building starts, or trust the lead.
   • Fix rounds: how many review → fix loops a slice may take before it is parked.
   • Clocks: a build clock and a review clock per slice, and a maximum wall-clock for the whole run.
   • Budget: a token ceiling per slice.
   • Keep this computer awake: Synergoi holds a sleep assertion for the run's duration.

4. Go to bed

   The run's access preset is yours to choose; anything outside it waits in the inbox until morning rather than guessing. Each slice builds in its own worktree.

The morning brief

The night-run pane shows every slice with its state — built, reviewed, verified, parked — the reviewer's and verifier's notes, and the lead's brief: what shipped, what didn't, what needs a human. From there you review each slice's diff in the Changes dock and land or ship it like any other thread.