Documentation
First-night safety checklist
Verify permissions, gates, stop behavior, recovery, Git identity, and review expectations before leaving a shift unattended.
Answers: unattended coding-agent safety checklist · Updated
Before the first unattended run, prove the exact environment with an attended small task: permissions work, gates run, STOP is honored, commits stay local, and recovery points to the same project.
Before arming
Use a trusted project and review every proposed gate and rule.
- Confirm the project and .nightshift workspace paths.
- Check Git identity and the branch you expect.
- Choose a small item with a fast, deterministic gate.
- Configure permissions for headless work.
- Set a deadline for open-ended work.
During the attended trial
Watch the complete loop once rather than only the final answer.
- The item is read before work begins.
- The gate runs immediately before commit.
- The commit stays local unless authorized.
- A genuine question is parked with a default.
- STOP leaves unfinished work open.
Before walking away
Clear test-only markers, confirm the watchman command and environment, and know where Status, Doctor, the parking lot, and the shift log will be in the morning.
Start with a bounded prompt
This prompt names the outcome and preserves Nightshift’s review boundary. Paste it into the supported coding host from the project you want to change.
Walk me through the Nightshift first-night checklist against this exact project and stop before unattended execution.What this workflow does not claim
- Passing the checklist in one project does not verify every other host, repository, or permission mode.
- The first unattended task should remain bounded and reversible.
Evidence and sources
These links support the released behavior, public outcomes, or problem language described on this page.
First-night checklistThe attended checks required before trusting an unattended run.Open evidence ↗Versioned setup skillThe shipped setup, workspace, rules, and first-run guidance.Open evidence ↗Versioned workflow contractThe shipped one-item loop, decision boundary, gates, recovery, and clock-out behavior.Open evidence ↗