% open nightshift
Nightshift
An AI that builds while I sleep — I fire it before bed and wake up to shipped, verified work and a morning briefing.
PROBLEM
The hours I'm away — asleep, on the golf course, playing a gig — are dead build time. And the slow part of building isn't usually the building, it's that I have to be in the chair to decide what's next and check it's any good. I wanted my away-time to actually produce things.
WHAT I BUILT
A loop I fire before I leave. It picks the highest-value item off my board, builds it, verifies it actually works, logs what it did and why, then pulls the next item — and keeps going until the token budget runs out. The last thing it writes is a one-page morning briefing that explains everything it shipped, in plain language, so I can catch up in two minutes over coffee.
HOW IT WORKS
It runs on guardrails, because unattended means no human to catch a mistake. Hard rules: no deploys, nothing sent externally, no deletes, and it only ever builds into new files — it never overwrites something that already works. It keeps a cross-shift memory file so it never rebuilds something it already shipped or reverses a past decision, and a 'do not touch' list pins anything that's live in production. Every item goes build → verify → log before it's allowed to move on, so the briefing I wake up to is work that's been checked, not just generated.
WHERE IT'S AT
Live, and genuinely used — I run it on real away-time. Each shift leaves a dated log of what it built, how it verified it, and a note on anything that needs my eye (like a draft in my voice it won't post without me).
WHAT I LEARNED
The unlock wasn't 'let the AI run wild' — it was the opposite. The value came entirely from the constraints: a clear definition of done per item, a verify step that has to pass, new-files-only so nothing live is ever at risk, and a memory so it compounds across nights instead of repeating itself. Autonomy is only useful when it's bounded enough to trust the output you wake up to.
STACK
Claude Code · autonomous agent loop · file-based memory · verify-before-next gates
$ /nightshift # autonomy: no deploy · no sends · new files only
[state] read memory · nothing to avoid rebuilding
[pick] a17 — 'how I build with AI' one-page SOP
[build] how-i-build-with-ai.md (the 5-stage build arc)
[verify] coherent · voice-rule held · ~620 words ✓ SHIPPED
[pick] next board item ...
[brief] morning briefing written · shift logged% cd ..