Use cases
Nightshift for Codex
Run durable, recoverable engineering shifts in Codex with native skills, gates, guards, scheduling, and watchman support.
Answers: Nightshift plugin for Codex · Updated
In Codex, ask Nightshift to set up and start from the project you want it to change. The plugin keeps the contract in project files, uses Codex-native skills and hooks, and can resume a recorded task when process and rollout evidence make recovery safe.
Start from the project
Open the project locally in Codex or connect Codex to its GitHub repository. Setup refuses to create durable-looking state in a disposable scratch conversation.
- Ask: “Set up Nightshift.”
- Add or approve the punch-list work.
- Ask: “Start the shift.”
- Use Status, Doctor, or Stop in natural language.
Permissions for commits
A shift whose contract creates local commits needs a permissions mode that can write Git metadata. Configure that before leaving; Nightshift’s own chosen guards still apply.
- Keep pushes explicit.
- Review the first run attended.
- Set an explicit deadline for open-ended work.
Codex recovery boundary
Same-conversation revival requires a recorded resumable task identity. A known non-resumable identity stands down rather than opening an unrelated task. Live API-wedge detection remains conservative.
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.
Set up Nightshift in this Codex project, propose the gates, and prepare one small attended task. Do not push or publish anything.What this workflow does not claim
- A Codex shift that commits needs a permission mode capable of writing Git metadata.
- Same-conversation recovery requires a recorded resumable task identity; uncertain cases stand down.
Evidence and sources
These links support the released behavior, public outcomes, or problem language described on this page.