Night Shift: your computer builds while you sleep

The most underrated resource in software is the eight hours your computer spends doing nothing while you sleep. Cloud agents monetize those hours for you — on their machines, with your code. OIOXO's answer is what we've come to call Night Shift: start a long build in the evening, on your own device, and read the results with your coffee. Nothing is uploaded, nothing is rented. It's your hardware doing the work, because the whole agent — model included — runs there.

This post is about what makes that actually work, and — because we'd rather under-promise — exactly what you need to keep in mind.

Why long runs usually die

An agent that runs for hours faces two killers: it forgets, or it stalls.

Forgetting is the context problem. Every model has a finite context window, and a naive agent loop just appends until it hits the wall and stops mid-thought. OIOXO's loop compacts as it goes: older turns are collapsed into a structured recap while recent work stays verbatim, so the agent keeps a durable sense of the goal without dragging the full transcript behind it. The session itself — goal, conversation, narration, build trajectory — is persisted on your device, so even a page reload doesn't decapitate the run.

Stalling is the judgment problem. Unattended, an agent can't ask you to approve every step, so it needs a finish line it can't argue with. That's the verified loop from the previous post: write, run, check against a real oracle (your tests, the type checker, the runtime), repair, repeat. When the agent gets stuck it tries diverse candidate fixes and lets the oracle pick; when a step budget runs out on honest progress, it continues rather than dying. Checkpoints are taken along the way, so morning-you can review what changed — and step back through it — instead of trusting a summary.

The honest checklist

We won't pretend a browser is a datacenter. For an overnight run in the web IDE:

• Keep the tab open. The model and the runtimes live in that tab. Close it and the shift ends (your session and files survive on disk — the run just pauses until you return).
• Keep the tab visible or in its own window. Browsers aggressively throttle background tabs to save power. A tab in its own window, left in the foreground, keeps full speed.
• Keep the machine awake and plugged in. Hours of on-device inference is real compute. Disable sleep for the night, and don't do this on battery — a laptop lid closing at 2 a.m. is the most common way a Night Shift ends early.

If you want the sturdier version of this, the desktop app is built for it: agents there run in the background on git worktrees, without a tab's lifecycle, and the CLI (oioxo code) runs in a terminal you can leave alone. Same loop, same verification, more forgiving host.

What you get in the morning

Not a "done!" message — a trail. The session records what the agent did and why, the checkpoints let you rewind to any point, and everything that claims to work has already been run against the oracle on the same machine you're sitting at. Diffs are yours to accept, not already merged behind your back.

And the part we care most about: at no point did your project leave your device. There is no server-side agent, no hosted workspace, no "we keep a copy so the run can continue." The run continues because your computer is running it. That's the trade Night Shift makes explicit — you supply the electricity and an open tab; nobody else supplies eyes on your code.

Your machine was going to be on all night anyway. It might as well come to work.