Documentation
Understand every part of the shift
Install Nightshift, write durable work, configure boundaries, schedule and recover shifts, read the report and receipt, and troubleshoot.
Start your first Nightshift
Install Nightshift in Claude Code, Codex, or Cursor, write one bounded task, run it attended, and review the local receipt before pushing.
Read page →02 · DocumentationInstall Nightshift
Install Nightshift for Cursor, Codex, or Claude Code and open the persistent project or folder you want it to work in.
Read page →03 · DocumentationHow Nightshift works
Understand the durable contract, one-item loop, gates, parked decisions, recovery, and morning handoff behind every Nightshift coding shift.
Read page →04 · DocumentationWrite a Nightshift punch list
Write a coding-agent punch list: complete, verifiable outcomes with Verify and Commit lines that survive long runs, compaction, and handoffs.
Read page →05 · DocumentationGates, guards, and stop rules
Choose verification gates and opt-in safety rules for an unattended coding-agent shift, including the clock-out hook that refuses an early stop.
Read page →06 · DocumentationClaude Code, Codex and Cursor crash recovery
When a coding-agent session dies mid-run, check the shift state, host signals, and recovery log, and learn when Nightshift resumes and when it stands down.
Read page →07 · DocumentationNightshift command reference
Choose the right Nightshift command for setup, execution, status, quality work, diagnosis, stopping, and archiving.
Read page →08 · DocumentationConfigure Nightshift safely
Set deadlines, stalls, command rules, path protections, identity expectations, and question-tool behavior.
Read page →09 · DocumentationSupported platforms and hosts
Understand Nightshift support across Cursor, Codex, Claude Code, macOS, Linux, native Windows, WSL, and remote environments.
Read page →10 · DocumentationRemote SSH, devcontainers, and WSL
Keep Nightshift’s host, project, state, and watchman on the same side of a remote environment boundary.
Read page →11 · DocumentationTroubleshoot a Nightshift run
Diagnose setup, gates, state, process leases, watchman behavior, and stop conditions without making the situation worse.
Read page →12 · DocumentationFirst-night safety checklist
Verify permissions, gates, stop behavior, recovery, Git identity, and review expectations before leaving a coding-agent shift unattended.
Read page →13 · DocumentationOwner rules: deny sudo, containers, installs
Configure rules.json: default-denied sudo, containers, global packages, daemons, and logins, plus optional guards, question parking, and the resolved view.
Read page →14 · DocumentationSchedule Claude Code or Codex to run at night
Print the launchd, cron, systemd, or Task Scheduler entry that starts a Nightshift at 04:05, after a preflight for queued work and headless permissions.
Read page →15 · DocumentationReceipts and what each item cost
Read the receipts an overnight coding-agent run writes as it works: one file per item, the verification that ran, the outputs, and the tokens and time it cost.
Read page →16 · DocumentationReview what Claude Code, Codex or Cursor did
Read the morning receipt, inspect the changes and checks, settle parked decisions, and find unfinished work before you accept an overnight coding-agent run.
Read page →17 · DocumentationArchive shift history and retention
File finished punch-list items, logs, snags, answered decisions, and receipts into dated archives, keep live files lean, and prune only on an explicit yes.
Read page →