Nightshift

In development

Windows desktop app · runs on your machine

A task card in the Nightshift dashboard. A green DONE badge sits beside the prompt that was asked. Below it, two panes side by side: on the left, inside a solid border with a blue left edge, a pane headed GIT FACTS · GROUND TRUTH listing the branch name, changed: 7 file(s), +802 -171, and the seven filenames. On the right, inside a dashed border, a pane headed CLAUDE'S CLAIMS with a grey UNVERIFIED chip, containing the assistant's written account of the work.
One job from last night. On the left, what git recorded. On the right, what the assistant said it did. Nightshift never mixes the two.

What it is

Fact

Nightshift does coding jobs while you sleep.

You write the jobs down during the day, in plain sentences. At night, Nightshift hands them one at a time to Claude Code — Anthropic's command-line coding assistant — and lets it work.

Every job runs on its own git branch. Your files stay as you left them until you read the result and decide to keep it.

It is a desktop app for Windows. There is no terminal to open and no account to make: the dashboard is a page served from your own computer. You need git and Claude Code installed already.

How a night goes

Fact
Evening

You add jobs to a list. Each one is a few sentences describing what you want changed. Drag them into the order you want them done in — that is the order they run in.

Overnight

Nightshift works the list, one job at a time, on its own branch. When Claude Code hits its usage limit, Nightshift waits the limit out and picks up where it stopped instead of giving up on the rest of the night.

Morning

One page shows every job. For each, you keep the work, throw it away, or send it back to be tried again. Nothing is merged into your project unless you say so, and discarding deletes nothing.

Facts and claims

Fact

A coding assistant can tell you it finished and have changed nothing.

It is not common. It is common enough that you cannot read a summary over coffee and go to work on it.

So Nightshift keeps two things apart. Git records what changed on disk: which files, how many lines. That can be checked. The assistant's account of what it did cannot be checked — it is a description, and descriptions can be wrong.

The dashboard draws the difference. Facts get a solid border. Claims get a dashed one and the word UNVERIFIED — every time, including when the claim turns out to be true. The label describes the kind of thing you are reading, not a suspicion about that particular job.

When a job reports success and the change is empty, Nightshift says so and holds the job for you to look at, rather than quietly merging it.

Git facts · ground truth
branch:  nightshift/20260804-011931
changed: 7 file(s), +802 -171

  README.md
  STATUS.md
  UI_SPEC.md
  nightshift.py
  server.py
  test_actions.py
  test_nightshift.py

Read out of git. Nightshift's verdict on the job comes from here and nowhere else.

Claude's claims Unverified

“I've implemented both changes. Here's what landed, and one thing I couldn't do.”

Written by the assistant about its own work. Useful to read. Not evidence of anything.

The two halves of the card above, with the rule spelled out.

Where it stands

Fact

Nightshift is in development. It works: it has run real jobs unattended, night after night, on the project that is building it.

Everything below is true today.

  • WorkingQueue, overnight runner, morning dashboard, keep and discard
  • Not yetAnything to download — the app is not packaged for anyone else's machine
  • Not yetA price, a licence, or a way to buy it
  • Not yetUsers other than its author, so there is nothing to quote and no numbers worth showing
  • Not yetA release date

What happens next

Unverified

“It'll be ready when the morning report is boring.”

That is a claim, not a fact, so it sits under a dashed rule like every other claim on this page. When there is something to download, this page will say so and the rule above will be solid.