Use cases
Nightshift for Claude Code
Run accountable engineering shifts in Claude Code with namespaced commands, hooks, scheduling, and recovery.
Answers: Nightshift plugin for Claude Code · Updated
Install the marketplace plugin, run /nightshift:setup, write or compose the work, then run /nightshift:start. The contract stays on disk while hooks enforce the enabled boundaries and the watchman handles classified recovery.
The command path
Claude Code exposes each Nightshift capability as a namespaced command.
/nightshift:setup
/nightshift:start
/nightshift:status
/nightshift:doctor
/nightshift:stopHeadless permissions
An unattended session cannot approve prompts. Setup can offer a project-local permissions setting; test it during an attended shift and keep the owner-defined guards active.
- Accept only the gates you need.
- Keep command and path rules understandable.
- Know the STOP path before leaving.
Reopen after revival
A headless worker can continue the recorded conversation while an already-open interface remains visually stale. Reopen the conversation before interacting; the process lease keeps the older process from performing observable tools.
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.
/nightshift:setupWhat this workflow does not claim
- An unattended session cannot approve permission prompts, so the first run should verify the chosen mode attended.
- A headless continuation may require reopening the recorded conversation before interaction.
Evidence and sources
These links support the released behavior, public outcomes, or problem language described on this page.