nightshift
GitHub
Menu

Accountable autonomous engineering

Give the agent the night.
Get back a reviewable morning.

Nightshift gives coding agents a durable punch list, owner-defined safety rules, recovery, and a clock-out gate—so long engineering runs keep working toward the contract instead of quietly stopping early.

Open GitHubInstall Nightshift ↓
  • MIT licensed
  • Local-first state
  • macOS · Linux · Windows
SHIFT 04 · 02:17 AM LIVE

Tonight’s contract

Release hardening

2/4
  1. ✓Repair the flaky release testcommitted · verified
  2. ✓Harden the recovery pathcommitted · verified
  3. 3Run the project gatesrunning checks now
  4. 4Leave the morning handoffwaiting in order
● The contract remains on disk through compaction and recovery.

INSTALL NIGHTSHIFT

One plugin.
Two native hosts.

Use the official OpenAI listing or copy the exact marketplace command for your coding host. Every path installs the same open-source package.

Open the official OpenAI listing ↗MIT licensed · no API key · no separate server

WHY NIGHTSHIFT

The working agreement lives outside the conversation.

A prompt can fade. A punch list, gate, decision log, and deadline stay inspectable.

01

Persistent contract

Open work survives compaction, restarts, and handoffs because the authoritative list stays in your project.

02

Mechanical boundaries

Opt-in hooks enforce the commands, paths, identity, and stop rules you choose before the run begins.

03

Morning receipts

Review local commits, verification results, parked decisions, snags, and recovery events in plain files.

ONE SHIFT, END TO END

Clear work in.
Inspectable evidence out.

Nightshift does not replace your coding host. It gives the host a durable operating contract and works one approved unit at a time.

Explore the complete lifecycle →
  1. 01

    Define the contract

    Write the outcomes, gates, commit intent, and any explicit deadline.

  2. 02

    Work one item

    Implement fully, verify immediately, commit locally, then tick.

  3. 03

    Park decisions

    Choose reversible defaults, record the reasoning, and keep moving.

  4. 04

    Review the receipts

    Inspect commits, checks, decisions, snags, and recovery events.

WATCH ONE SHIFT

The gate refuses an early clock-out.

A real session, unedited apart from pacing: three items, one commit per item — and midway the agent declares itself finished with two boxes still open. The gate hands back the contract; it clocks out only once the list is clear.

READY-MADE ENGINEERING SHIFTS

Search the problem.
Start from a bounded contract.

Browse every ready shift →
FINITE SHIFT

Finish the todo list

Turn approved work into ordered outcomes with one local commit and gate per item.

Build the contract →OPEN-ENDED

Evolve the product

Research the product, rank evidence-backed opportunities, and ship the strongest complete work within the clock.

See product evolution →QUALITY

Clear quality debt

Survey tests, code, accessibility, contracts, documentation, dependencies, and security.

Open the quality guide →RECOVERY

Revive after API Error 500

A watchman detects the dead session, waits out the outage, and resumes the same conversation — the 3 AM failure no longer ends the night.

See how revival works →TESTING

Increase test coverage overnight

Use Codex or Claude Code to add behavior-protecting tests without padding a percentage.

Open the coverage shift →CONTINUITY

Keep Codex on task after compaction

Preserve the current phase, rejected paths, next action, and verification outside conversation history.

Preserve the checkpoint →

RECEIPTS, NOT PROMISES

A 45-hour contract.
Six roadmap phases.
One reviewable handoff.

The evidence library follows the work from punch list to a human-reviewed 67-commit pull request covering 57 closed issues.

Read the receipts →
45h

continuous contract

67

reviewable commits

57

issues closed

6

roadmap phases

THE SHORT ANSWERS

Before you leave an agent with the night.

Read every answer →
What does Nightshift actually do?

It gives Codex and Claude Code a durable punch list, opt-in mechanical rules, recovery, and a clock-out gate for accountable long engineering runs.

Does it push or merge code?

Not by default. Nightshift leaves local commits for owner review unless the shift contract explicitly authorizes an external action.

Does the gate prove the code is correct?

No. The gate prevents approved work from being quietly abandoned. Item definitions, project checks, and human review prove quality.

Should my first shift be unattended?

No. Run one small task attended so you can verify permissions, gates, stop behavior, and recovery in your exact environment.

THE FIRST SHIFT CAN BE SMALL

One task. One gate.
One reviewable morning.

Open GitHubInstall from OpenAI ↗