Nightshift
In development Join the waitlist

Windows desktop app · runs on your machine

Coding jobs run overnight. In the morning, you see exactly what changed.

Nightshift works through your queue with Claude Code while you sleep, then shows what actually changed beside what the assistant says it changed.

Two panes from a finished job in the Nightshift dashboard. Left, inside a solid border with a blue left edge: GIT FACTS · GROUND TRUTH, the branch name, changed: 7 file(s), +802 -171, and the seven filenames. Right, inside a dashed border: CLAUDE'S CLAIMS with a grey UNVERIFIED chip, and the assistant's written account of the same work.
One finished job. Left, what actually changed — solid border. Right, what the assistant said it did — dashed border, labelled unverified. The two never blend into one sentence.

What it does

Fact
Evening

You write down the jobs you want done, in plain sentences, and drag them into the order they should run.

Overnight

Nightshift runs them one at a time, each on its own git branch. When Claude Code hits its usage limit, it waits the limit out and picks up where it stopped.

Morning

One page, every job. Keep the work, discard it, or send it back to be tried again. Nothing is merged unless you say so, and discarding deletes nothing.

It runs on your own computer — no terminal to open and no account to make. You need git and Claude Code installed already.

Why it works this way

Fact

An assistant can report success and have changed nothing.

So the report keeps two things apart. Git — the standard tool that records every change made to a project — says exactly which files changed and by how much. That can be checked. The assistant's account of its own work cannot.

Claims are drawn dashed and labelled UNVERIFIED every time — including when they turn out to be true. And when a job reports success with an empty change, Nightshift holds it for review instead of merging it.

Where it stands

Fact

Release is close.

The engine and the app are built and tested, and they have run real jobs unattended, night after night. What is left is a polish pass and signing the build so Windows stops warning about it on first launch.

  • WorkingA queue you drag into the order the jobs should run in
  • WorkingUnattended overnight runs — one job at a time, each on its own git branch
  • WorkingWaiting out Claude Code's usage limits and picking up where it stopped
  • WorkingVerdicts read from git — a success report with an empty change is held for review, never merged
  • WorkingThe morning dashboard: keep, discard, try again — discarding deletes nothing
  • WorkingA double-click Windows app with a folder picker, no terminal involved
  • WorkingWorking files kept outside your project, so its git status stays clean
  • Not yetA download — the build is unsigned and not published anywhere
  • Not yetA price, a licence, or a way to buy it
  • Not yetOutside users, so there is nothing to quote and no numbers worth showing
  • PlannedNovember 7, 2026 — the date the release is aimed at

What happens next

Unverified
Releasing November 7, 2026.

That is the date the work is aimed at — a plan, not something that has happened yet — so it sits under a dashed rule like every other claim on this page. Join the list and you'll get one email when there is a build to download.