Use cases
Nightshift plugin for Claude Code
Install Nightshift in Claude Code, prepare a bounded contract, diagnose early stops, and review recovery and morning evidence.
Updated
What does Nightshift add to Claude Code, and how do I start?
Install the marketplace plugin, open the real project, run /nightshift:setup, write approved outcomes, and run /nightshift:start. Claude Code hooks return open items on ordinary completion; a separate watchman handles classified failures.
Install and start in Claude Code
Run the two marketplace commands in Claude Code, then Setup in the persistent project. Review gates and permissions before the first attended shift.
/plugin marketplace add orwa-mahmoud/nightshift
/plugin install nightshift
/nightshift:setup
/nightshift:startWhen Claude Code stops
A normal attempted end with open approved items gets the contract again. Escape and an owner STOP remain valid interruptions; permission waits and usage limits require their own diagnosis. API Error 500 is an upstream service failure, which the watchman can retry through only when evidence supports revival.
Review before accepting
Check the receipts, commit diffs, gate results, and parked decisions. A recovered headless conversation may leave an old panel visually stale; reopen it before sending another message. The public Claude Code-to-Cursor case shows a handoff after an owner stop, followed by human review.
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.