Night Shift

Each slip is one change the loop built and I accepted, stamped with its review. Fourteen nights of them, Nº 12 to Nº 103, replayed from the ledger under each night’s moon. Every receipt, listed.

Most of a good loop is what you leave out.

For developers who already run coding agents: one Fedora VM, a loop that builds while you sleep, and a source and a reason for every idea in it.

The kit. From $99, once.

Kept, changed, left out

The field ships a new idea every day. Each one here was read at its source and weighed against the loop’s own record, then kept, changed or left out. The tags say who it came from and when it landed.

  • kept

    Fresh eyes

    Every build ends with the builder rereading its whole diff as if someone else wrote it.

    From Jeffrey Emanuel’s Agent Flywheel.

    Read 8 October, in the kit 10 October.

    Why, in full
  • kept

    Intent is the constraint

    Our ledger fits it: over five days in October, building took about 5% of the loop’s time. So the kit keeps one build slot and spends the effort on the spec.

    From Jaka Hudoklin, replying in an X thread on software factories.

    Read 13 October.

    Why, in full
  • kept

    Design skills against generic pages

    The kit’s installer pins three of them for your Claude Code sessions.

    From Impeccable by Paul Bakaus, taste-skill by Leonxlnx and Emil Kowalski’s skills.

    Read and in the kit 19 October.

    Why, in full
  • kept

    A browser for your Claude Code sessions

    The same installer adds Playwright MCP to your host Claude Code sessions, so Claude can open the page it built and look before you do.

    From Microsoft’s Playwright team.

    Read and in the kit 19 October.

    Why, in full
  • changed

    Spec review before the build

    The flywheel polishes a plan with several models until it stops changing. Here one other model family reads each medium or large card Claude writes, and the card cannot be queued until that reader says it is ready, or you waive the read.

    From Jeffrey Emanuel’s Agent Flywheel.

    Read 8 October, in the kit 10 October.

    Why, in full
  • changed

    The person sits at the plan

    The flywheel keeps no approval gate on the diff. Here cards you pre-approve, in repositories you mark low-risk, may merge overnight. It ships switched off, and changes to the loop itself always wait for you.

    From Jeffrey Emanuel’s Agent Flywheel.

    Read 8 October, in the kit 11 October.

    Why, in full
  • left out

    Agent swarms on one branch

    They assume someone tending agents every 10 to 30 minutes. Our queue is short, and over five days in October building took about 5% of the loop’s time, so one build slot does the work.

    From Jeffrey Emanuel’s Agent Mail and bv.

    Read 8 October.

    Why, in full
  • left out

    Session search and memory tools

    The ledger already records every attempt, review and receipt, so a second index was not needed yet.

    From Jeffrey Emanuel’s cass and cm.

    Read 8 October.

    Why, in full
  • left out

    Copying another site’s design

    Website-copier skills start you from someone else’s page. The design skills above start from your subject instead.

    From website-copier skills in a round-up of design tools.

    Read 22 October.

    Why, in full

A credit names where an idea came from. None of these people has endorsed the kit.

Fourteen nights

83

cards merged into its two repositories, the kit and this page, 8 to 22 October 2026

87%

published on the first attempt: the box pushed a candidate without a retry

10¢

metered model spend in two weeks, on top of two flat-rate plans

First, a card is cut.

Goal, scope, acceptance test.

Then a box builds it.

No network, no secrets, one key.

Another family reads it.

Codex builds, Claude reviews.

You turn the key.

Accept, install, receipt printed.

One card’s night

Nº 102, from the box to master in 37 minutes, as the ledger recorded it.

  1. Built 19:52 Claimed by the tick. Codex builds it in a sealed box.
  2. Published 20:06 The tests pass with no network, and the candidate is published.
  3. Reviewed 20:08 Claude Opus reads the diff: merge.
  4. Accepted 20:21 The suite passes on the base and on the merge. Receipt Nº 102 is printed.
  5. Installed 20:28 Installed on master, fast-forward only.
The whole workshopThe kit’s own generator draws a card’s journey and the system map from its configuration. See the system Every receiptThe ledger annotated, with the card and the receipt you touch: base, merge, reviewer and cost for each. Read the ledger

What the box refuses

  1. Every card builds in a sealed box: no network beyond its engine’s own API, no secret beyond its own key, a read-only root.
  2. Another model family reviews every medium, large or security card; a small one waits for your own read.
  3. Nothing lands on master until you accept it, or pre-approve it.
Read the whole label

Drop 01

The kit you buy is the first drop: the loop, the guide and every idea above that was kept or changed.

Personal and Team copies get every drop for 12 months; that is what updates means on the ticket. A drop carries the next picks into the code and the guide; the receipts that put them in, and what was left out and why, are published here.

It arrives by email as a git bundle packed on top of the one you have, so your loop takes it as ordinary history when you merge it. The drops log.

Packing slipOctober 2026
As of
22 October 2026
Last receipt
Nº 103
Ideas in
6, kept or changed
Left out
3, with reasons in the notes
Files copy
This drop
Personal, Team
Every drop for 12 months
Arrives
By email, as a git bundle

The kit

  • The guide and the repository
  • Personal and Team: updates for 12 months; the build stays yours after
  • Pay once, run it on your machines
  • Team covers up to five developers in one company
  • Launch prices until 31 December 2026
  • Sold through Paddle, which handles tax and refunds
  • Arrives by email as a git bundle within one working day; updates come the same way

You bring

  • One Linux VM under VMware, VirtualBox, Hyper-V or KVM, on a Mac, Windows or Linux host. We run Fedora 44 with four CPUs, 16 GB of memory and a 100 GB disk; the installer also supports Ubuntu 26.04 and Debian 13.
  • Your own Claude Code and Codex plans (we run Claude Max and a ChatGPT plan). Model spend stays on your accounts; the kit adds no fee.
  • Optional: a Surplus key with a few dollars of credit, for the Hermes agents and cheap marketplace builds; a Telegram bot, free from BotFather, to put the morning brief, the health alert and the deadman on your phone. Without them the loop runs on the two plans and reports on the VM.

Files

$99

as it is on the day

Get the Files kit

Personal

$249

list price $299, 12 months of updates

Get the Personal kit

Team

$499

list price $599, 12 months of updates

Get the Team kit

Before you buy

Does it run on a Mac?

In a virtual machine on one. The loop runs inside a Linux VM under VMware, VirtualBox, Hyper-V or KVM, on a Mac, Windows or Linux host. We run Fedora 44 on x86-64; the installer also supports Ubuntu 26.04 and Debian 13, so far tried in containers rather than on a VM. An arm64 image on Apple silicon is untried.

Can I use Docker instead of podman?

No. The sealed boxes and the workshop’s secrets are podman’s, and Docker is not supported.

Do I need both a Claude and a ChatGPT plan?

Yes: Claude Code and Codex build, and each reviews the other’s work. Both bill you directly; the kit adds no fee of its own. A Surplus key is optional: it adds the Hermes agents (a dispatcher, research workers and the phone relay) and cheap marketplace builds.

Is running Claude Code overnight on my own plan allowed?

You sign in to the unmodified Claude Code with your own plan, which Anthropic’s compliance page allows, and the usage bills to you, never through us. The same page says plan limits “assume ordinary, individual usage”, so the loop builds one card at a time and stops when a plan says stop instead of working around it.Read Anthropic’s page.

What happens when a plan hits its usage limit?

That engine pauses for 30 minutes after the refusal and the card goes back in the queue; the attempt does not count against it. The loop board shows the pause.

What leaves my machine?

Your model calls, to the providers you sign in to; your Telegram messages, if you connect a bot; pushes to your own git remote; and backups to your second machine, if you turn them on. The kit itself sends nothing to DW Digital: no telemetry and no licence check. The tools it installs follow their makers’ own policies.

Can I read the guide before buying?

The short version is on this site: what you need, the first hour and what runs when. The full guide, with every command, ships with the kit.Read the guide.

Isn’t this just a bash loop?

The schedule is the easy part: every 15 minutes a timer starts one card. What you pay for is everything around it: a sealed box for each build, a second model family reading the diff, your accept, and a numbered receipt for each change. 103 receipts so far, each one on the ledger.Read the ledger.

What if you stop selling it?

It keeps working. You get the full repository, with no licence check and no phone-home, so nothing of ours has to stay online. New drops would stop; your loop would not.

Can I get a refund?

Refunds follow Paddle’s policy as the merchant of record. If something does not work as the guide says, email me first; I would rather fix it.

What a night costs

Move the sliders. Marketplace models billed about a cent per small card in our October 2026 ledger. For frontier models we assume four dollars per card at list price, more than the ledger’s own averages, and a flat-rate plan absorbs it.

6
30%
$0.05metered, per day, billed
$7.20frontier at list, per day, covered by flat-rate plans

Illustrative. Your cards, models and prices will differ; the guide shows how to measure your own.

Picked after hours, in Ohio.

Email me

Who picks

I’m Dan White, an infrastructure engineer. For a decade I’ve read what the best developers try next, much of it on X, and kept the little that survives a real loop. Every idea kept here ran on this loop first.

What you get

The loop I run, written down and runnable. The dated record of what went wrong and what changed is public here, in the receipts, the notes and the drops. New picks arrive as drops. Not a course, not an agency. Set-up help is separate.

Pay once. Read the guide tonight, run the loop tomorrow. ORDER