Night Shift

A Night Shift hands a goal to a crew of agents and lets them work while you sleep: someone plans the slices, someone builds them, someone checks each one, and the lead leaves a morning brief you read with your coffee.

Starting a shift

1. Press the moon

   The moon button in the composer turns that one message into a shift. The composer tells you what it is about to do; press it again to go back to an ordinary chat.

2. Write what done looks like

   A paragraph, a checklist, a pasted ticket, or a path to a PRD in the repo. This is the one thing worth being fussy about: the plan the lead writes is only as good as the goal you gave it.

3. Name the crew with @

   @claude to plan, @codex to build, @grok to check — the roles bind to who you named, in order: Plan, Build, Check. Mixing vendors is the point, because no single quota then has to carry the whole night. Name one provider for everything and the composer says out loud that it will be reviewing its own work.

4. Say where it should land

   Either merge into main when the shift finishes, or keep the branch so nothing moves until you have read it. The choice is saved with the run, so a recovery or a continuation cannot quietly change it.

5. Start it

   ⌘Enter (or CtrlEnter) starts the shift. Enter is still just a newline, so nothing launches by accident. If the project needs Full auto consent, you are asked for it here; a refused start keeps your goal and your choices in the composer.

While it runs

The shift appears as a card in the conversation that started it, with its own clock and the task it is on. Each slice builds in its own worktree, so a half-finished slice never leaks into the next one, and the shift keeps roughly twenty minutes in reserve to integrate and write the brief rather than being cut off mid-sentence. If a slice has less than half an hour of budget left, the remaining work is held for tomorrow instead of being rushed.

• Failover stays inside the provider you asked for. If the account you named hits a wall, the shift can move to another of your connected accounts on that same provider. It will not silently swap in a different vendor, and it will not turn your three-model crew into one model reviewing itself.
• Your access preset still rules. A shift never widens its own permissions; anything the preset forbids waits in the inbox for morning.
• Keep this computer awake holds a sleep assertion for the shift's duration — worth checking before you close the lid.

The morning brief

Open the run's card, or its details tab, for every task with its state, the reviewer's and checker's notes, and the lead's brief: what shipped, what didn't, and what needs a human. The changes are pinned to the exact commit range the shift produced, so reviewing them in the Changes dock shows you the night's work and nothing else — then land or ship it like any other thread.

If you have the paired iPhone companion, the notification opens that exact run even if another shift has started since. Pushing from the phone shows you the destination, the immutable commit and the diffstat, and then asks a second time before it does anything. The engine re-checks the commit and refuses if new work has landed on top; no credential is ever copied to the phone.