Use cases
Nightshift plugin for Codex
Install Nightshift in Codex, start a bounded task list, inspect recovery limits, and review the local result.
Updated
What does Nightshift add to Codex, and how do I start?
Install the plugin, open the persistent project in Codex, ask Nightshift to set up and start, then inspect the work contract and receipts. Codex-native hooks return open items on an ordinary stop; recovery requires host-specific process and identity evidence.
Install Nightshift in Codex and start
Use the official Plugin Directory or the Git-hosted marketplace install for local Codex. Ask Nightshift to set up this project, review the proposed rules, add a small item with Verify and Commit lines, then ask it to start. A commit-making shift needs permissions that can write Git metadata.
What Codex can keep
The punch list, decisions, snags, and item receipts live on disk through context compaction. On an ordinary stop, the hook returns approved open items. A dead process may be revived if rollout and process evidence permit it; SessionEnd pauses recovery, and same-conversation revival needs a resumable task identity.
Review the run
Use Status or Doctor if progress seems stalled. Reopen a recovered Codex task before interacting with a stale panel, then inspect the local diff, checks, decisions, and morning receipt. A tick is the agent's report, not independent proof.
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.