Telling Technology · Learning in public
All episodes
EP.07 — NIGHT SHIFT
A Claude Code workflow, while I sleep

The night shift

I told an AI my idea at half past eight in the evening. It asked me six questions. I answered two from the couch and fell asleep. At one in the morning a fresh session read the brief and built this whole page on its own — then left me a note listing every guess it made. The page you're reading is the page it built.

A dark room at 01:00, a laptop glowing with a terminal building a web page on its own, the chair empty
⌁ 20:30 ask · 01:00 build · 08:00 handoff · 0 keystrokes overnight
it started with a buzz on my phone at half past eight
01 20:30 · the ask

My phone buzzed: "building this tonight — 6 questions"

Every evening at 20:30 a scheduled script wakes up, reads the backlog, picks the next idea, and texts me a short brief on Telegram: here's what I'm building tonight, here are the few things I need to know. Episode number, tone, who it's for. Six questions, no app to open — just reply in the chat.

nightly-ask.ps1 — 20:30
> pwsh nightly-ask.ps1 → Telegram
🌙 Building tonight: "The night shift — a site that builds itself while I sleep." 6 quick questions before 01:00. Answer what you can; I'll best-guess the rest and log every assumption in the morning.
A Telegram message at 20:30 listing six questions about the episode to build tonight
20:30 · Telegram
the nightly ask — six questions, sent to my phone
02 21:00 · the answer (or not)

I answered a few, half-asleep — that's allowed

The deal: I answer from the couch, or I don't. If the questions sit there, the build runs anyway on best guesses. Tonight I tapped out a handful of replies — make it episode six, yes put the real brief on the page, keep the same tone as the others — and let the rest ride. Whatever I skipped, the morning note would tell me what it decided for me.

Telegram — my replies
> "this is episode six." · "yes, why not — put it on the page." · "same tone as the others."
Logged ✓ — answers written back into the brief as plain text. Building at 01:00. Sleep well; the rest I'll best-guess and confess in the handoff.
A Telegram thread with three short replies answering the nightly questions
21:00 · a few taps
answers land back in the brief as plain text
03 01:00 · the build

A fresh session woke up and built the whole page

At one in the morning a second scheduled script opens a brand-new AI session with one job: read tonight's brief, read my answers, and build a complete episode page from the template — hero, story beats, gallery, downloads, the lot. It writes the unpublished video script too, renders desktop and mobile snapshots, and commits the result locally. No one is watching. The page you're reading right now is the page it built.

nightly-build.ps1 — 01:00
> pwsh nightly-build.ps1 → fresh Claude Code session
● Read brief 2026-06-06 ✓ · chose slug night-shift ✓ · filled every token (0 left) ✓ · wrote video script ✓ · rendered 2 PNGs ✓ · committed locally ✓ — handoff ready for 08:00
A terminal at 01:00 building an episode page step by step, unattended
01:00 · unattended
one brief in, a full episode out — while the room was dark
⚠️

It never stops to ask — it guesses, then confesses

The rule for the night shift is simple: never block on a question. If something's unclear at 01:00, it makes the best call and writes it down. Every guess lands in the morning handoff under "Assumptions" — so I wake up to a finished page and an honest list of what it decided without me. Status: PENDING → BUILT.

✦ the recursion · this is the real exchange

Yes — tonight's actual brief is on the page

You asked whether the live brief and my Telegram answers should appear on the episode they produced. They should. Here are the six questions it sent at 20:30 and my verbatim replies — the exact input that built everything above and below.

1 · Which episode number should this be?
"If number four is my own design, episode five is the plane globe, then this must be episode six."
2 · Should tonight's brief and Telegram exchange appear on the page as a live exhibit?
"Yes, why not?"
3 · Write the full video script tonight, or hold it until you've seen the page?
"You can create the script, but I want to see the page first."
4 · Tone — technical, narrative, or both?
"Same tone as the previous episodes — that 'I woke up to something newly created' feel, then break down exactly how people can replicate it."
5 · Include a visible "what the AI assumed" log on the page?
"Yes."
6 · Audience — other developers, or general "AI is wild" viewers?
"Anyone wanting to learn and try at home — with click-to-copy links so they can put the resources on their own page."

What the night shift assumed (and you can override)

  • ▸Slug & tag: chose night-shift / EP.06 from your "episode six" answer — bumped to EP.07 on publish.
  • ▸Channel: mode B (film later) per the brief — wrote the on-camera script but left the video slot hidden.
  • ▸Images: hero, the two Telegram shots, the build shot, four gallery files, the handoff and the teaser don't exist yet — placeholders point at descriptive filenames; generation prompts are in the morning handoff.
  • ▸Download links: the GitHub URL for the engine is a best guess — confirm or swap it before publish.
  • ▸Cliffhanger: guessed the next episode is "the night shift starts posting" — change if Ep.08 is something else.
04 the receipts

Four files, made while I slept

Everything the night shift touched is a real file on disk, timestamped overnight. Tap any image to enlarge it and read exactly what it is.

The nightly brief markdown file with the package and six questions
the brief it read
The Answers section of the brief with verbatim Telegram replies
my answers, pasted in
The finished episode page rendered to a desktop snapshot
the page it built
The morning handoff markdown listing what was built and assumed
the morning handoff
BUILT OVERNIGHT · 08:00 HANDOFF

I woke up to a finished page and a note saying what it guessed

At eight, before coffee, a morning handoff was waiting: what it built (this page plus the video script), what it assumed (every guess, one line each), and what it still needs from me (a few images to generate, the video to film, one hidden slot to unlock). I didn't write a single line of this overnight. I read the note and pressed publish. That's the whole job now — review, not build.

A morning handoff note on screen at 08:00 listing what was built and assumed, coffee beside the laptop
brief 2026-06-06 · 1 build session · 0 keystrokes between 21:00 and 08:00
06 Steal this

Build your own night shift

Two scheduled scripts, a brief/handoff format, and the episode template. It runs on Claude Code + a Telegram bot + Windows Task Scheduler (or cron). Everything here is free and open — clone it, point it at your own backlog, make it yours.

skill /bitesize → backlog cmd nightly-ask.ps1 · nightly-build.ps1 template episode-template.html format brief + handoff
schedule the 20:30 ask schtasks /create /tn "nightly-ask" /tr "pwsh nightly-ask.ps1" /sc daily /st 20:30
↧ Get it on GitHub ⎘ All episode downloads

⧉ Copy a link to put on your own page

Building in public too? Grab any of these and drop it straight into your own site or notes — one click, no typing.

Nightly engine https://github.com/jacobskogstrom/nightly-story-engine
Episode template https://github.com/jacobskogstrom/nightly-story-engine/blob/main/episode-template.html
This episode https://tellingtechnology.pages.dev/episodes/night-shift.html

No GitHub? Comment NIGHT on the post and the bot DMs you the link.

Next episode

Next: the night shift starts posting without me

It can build the page while I sleep. The last gap is the upload. Next episode I hand it the keys to the channels — caption, schedule, cross-post — and find out what it does when nobody is awake to approve the draft.

Teaser: scheduled posts firing to TikTok, Reels and Shorts overnight while the room is dark
drops next · follow @bitesizeai so you don't miss it