nightshift

Arm a nightshift shift with a punch list of tasks in .nightshift/punch-list.md, then let the agent work items top to bottom. A clock-out gate blocks stopping until every box is ticked, and receipts plus a morning page record what was delivered.

A punch list is a markdown contract of checkbox tasks, each with its own Verify and Commit lines, stored at .nightshift/punch-list.md. The agent works one item at a time, runs the gate before each commit, and cannot delete items or edit the contract to end the shift early.

Yes, nightshift supports Claude Code, OpenAI Codex, and Cursor through host-specific watchman and permission setups. Codex shifts that commit need danger-full-access because workspace-write protects .git, while Cursor arms its own watchman with a recorded conversation id.

A watchman process detects crashed sessions and revives them using the recorded session id, falling back to a fresh session that resumes from the punch list. Progress survives on disk through receipts, the shift log, and per-item commits.

Question tools are denied during a shift, so the agent chooses a sensible production-grade default and records the decision with reasoning in parking-lot.md. The owner reviews parked decisions in the morning rather than being woken by questions.

Avoid it for actions outside the coding boundary such as publishing, merging, deploying, deleting production data, or spending money, which still require the owner. It also requires a persistent project workspace, not a disposable scratch environment.