Use cases
Nightshift plugin for Cursor
Install Nightshift in Cursor, start from a persistent project, understand Cursor-specific stops, and inspect IDE-to-CLI recovery limits.
Updated
What does Nightshift add to Cursor, and how do I start?
Install the released Cursor plugin, open the actual project, run Setup and Start, and keep the punch list on disk. Cursor's stop payload distinguishes completed, aborted, and error; an IDE crash can hand the contract to a separate CLI worker when evidence permits.
Install the native Cursor plugin
In Cursor, use Customize → Add → From GitHub Repository to import https://github.com/orwa-mahmoud/nightshift, then install Nightshift from that imported marketplace. Open the persistent project before Setup, approve useful gates, add one bounded item, and test Start attended. The Cursor Directory page is a discovery listing.
Diagnose Cursor's stop status
Completed with open boxes keeps the contract active. The Stop button reports aborted and leaves the list for later; an error needs investigation. A question or approval wait is not early completion. Use the host-specific checklist before changing a rule.
Understand the recovery boundary
Cursor IDE conversations and CLI sessions have separate stores. After a proven IDE death, Nightshift can mint a CLI worker that reads the same contract; it cannot claim the CLI worker is the same IDE chat. Cursor CLI currently needs project .cursor/hooks.json, which Setup offers to copy on approval. Review the worker's diffs and receipts before accepting the result.
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.
Open the project in Cursor, install Nightshift from its public directory listing, run Setup, and prepare one small attended shift before enabling unattended recovery.What this workflow does not claim
- Cursor IDE Agent and Cursor CLI use different conversation stores; Nightshift never claims that a CLI worker resumes the same IDE chat.
- The Cursor CLI currently needs explicitly offered project hook wiring for headless shift mechanics.
Evidence and sources
These links support the released behavior, public outcomes, or problem language described on this page.