Use cases
Run Nightshift without a Git repository
Use a persistent notes folder for research, SEO, documentation, and other artifact work, with reviewable receipts instead of commits.
Answers: use a coding agent without a Git repository · Updated
Nightshift does not require every shift to modify code. Setup can select artifact mode for a durable non-Git folder, preserve the contract and decisions on disk, and write completion receipts for compatible research and writing shifts.
Use a persistent folder, not scratch space
Open the real folder in the supported coding host. Setup records artifact mode and a receipts location without running git init merely to imitate repository work.
- The folder must survive the conversation.
- Receipts need a usable real directory.
- Temporary ChatGPT scratch workspaces remain refused.
Choose artifact-compatible work
Research synthesis, cited documentation writing, SEO auditing, and owner-defined writing can end in artifacts. Repository-only catalog entries are skipped when they cannot run honestly.
- No fake commit requirement.
- No repository tooling assumed.
- The item gate still runs before a receipt is accepted.
- Automatic Hunt ranks only work the target supports.
Review and archive the evidence
Each completed item writes a receipt naming the output, checks, decisions, and remaining limitations. Archive can copy those receipts into the dated run history while leaving the live output available.
Set up Nightshift in this persistent notes folder for artifact work. Use local receipts, do not initialize Git, and propose only compatible research, documentation, or SEO shifts.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 artifact mode for this persistent folder. Use local receipts instead of commits, choose only artifact-compatible shifts, and archive the completed receipts when the run is reviewed.What this workflow does not claim
- A disposable scratch workspace is still refused because its state and receipts would not be durable.
- Repository-only shifts such as coverage, dependency upgrades, and code defect repair are skipped when no compatible work target exists.
Evidence and sources
These links support the released behavior, public outcomes, or problem language described on this page.