Project

About Nightshift

Why Nightshift exists, what it guarantees, what it deliberately does not claim, and how to contribute.

Answers: what is Nightshift coding agent plugin · Updated

SHORT ANSWER

Nightshift was built after long coding-agent runs repeatedly completed easy work, deferred the hard items, paused for questions, or disappeared with the objective trapped in conversation history. Its answer is a durable contract with reviewable evidence.

01

The problem

Repeating “keep going” does not make an instruction durable. Long sessions compact, processes die, questions block, and an agent can decide that the difficult half deserves another session. Nightshift moves the agreement outside that volatile context.

  • The list remains authoritative.
  • Questions park instead of consuming the night.
  • Dead sessions can recover conservatively.
  • The morning handoff is inspectable.
02

The design boundary

The tick is self-reported by design. A second ceremony performed by the same model would not create independent proof. Sharp definitions of done, project checks, local commits, and owner review are the honest quality system.

  • Guards are opt-in rules, not a sandbox.
  • Recovery does not repair conversation history.
  • No support is claimed for unverified environments.
  • Publishing remains explicit.
03

Open source

Nightshift is MIT licensed. Human and AI-assisted contributions are welcome across catalog entries, documentation, tests, runtime, recovery, hooks, platforms, and public run evidence.

  • Catalog shifts are small, focused contributions.
  • Public claims follow released behavior.
  • Local run history remains private by default.
TRY IT

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.

Explain whether Nightshift fits my project using its released behavior, boundaries, and public receipts—without starting or changing anything.
BOUNDARIES

What this workflow does not claim

  • The clock-out tick is self-reported by design; Nightshift does not claim independent proof.
  • Current public work is the MIT plugin; no unreleased product or support claim is implied.
SOURCES

Evidence and sources

These links support the released behavior, public outcomes, or problem language described on this page.

Versioned workflow contractThe shipped one-item loop, decision boundary, gates, recovery, and clock-out behavior.Open evidence ↗MIT licenseThe license distributed with Nightshift v0.14.3.Open evidence ↗Merged 67-commit flagship PRGitHub records 67 merged commits across the six documented phases.Open evidence ↗
RELATED QUESTIONS

Continue from the question you have

why coding agents stop earlyRead the answer →how Nightshift worksRead the answer →where Nightshift run evidence is publishedRead the answer →