Go to bed. Wake up to a pushed branch

Give Claude Code or Codex the refactor you keep postponing, close the laptop and sleep. Your Compute runs the agent, the tests and the database all night, on your own subscription. Pro is $75 a month, flat.

Get my Compute See the plans

From $39 a month · Docker and sudo included · Cancel from the dashboard any time

23:40

dev@night-shift:/work/shop$ claude "split orders.go into a package, keep the API, make every test pass"

▸ reading internal/orders (41 files)

▸ docker compose up -d postgres redis

▸ go test ./... FAIL 12 tests

02:15

▸ moving pricing rules → internal/orders/pricing

▸ go test ./... FAIL 3 tests

05:52

▸ go test ./... ok 214 tests

▸ git push -u origin orders-split

✓ done: 38 files changed, branch orders-split pushed

The big refactor keeps sliding to next week

It's hours of agent time: read forty files, move the code, run the suite, fix what broke, run it again. Start at 5 p.m. and the laptop has to stay open, awake and online until it's done.

So the refactor waits for a quiet weekend that never comes. Meanwhile your five-hour window refills at 2 a.m. and nobody spends it.

One night, lid closed

23:10
Hand over the whole job
Open a tab in the project and give the agent the full task: split the package, keep the API, make every test pass.
23:12
Close the laptop
The tab was a window onto a tmux session. The session keeps running on your Compute, with Postgres and Redis in Docker beside it.
02:15
Red tests are the agent's problem
Twelve tests fail at 2 a.m. The agent reads them, fixes the code and runs the suite again. Approvals are off, so nothing stops to wait for your permission.
07:50
Read the branch with coffee
Open the dashboard on your phone or laptop. You land in the same session with the full scrollback: branch pushed, tests green.

The night works for you

Eight hours of agent time you were leaving on the table
The agent works while you sleep, and the morning starts with a finished branch to review. Ship twice as much without working twice as long.
The real stack, all night
Docker Compose runs Postgres, Redis and your services next to the agent, so the tests that go green at 3 a.m. ran against the real thing.
A run nobody has to babysit
Every agent CLI comes with approvals off, so the run keeps moving at 1 a.m. while you sleep.
Every step in the scrollback
Scroll up in the tab and see why the agent moved each file before you merge a line of it.

The size for this job

Pro · $75

4 vCPU and 8 GB run the agent, a full test suite and two databases at once, with room left for the build.

Manifestdetachbox · node 1

Compute: night-shift
Projects: /work/shop
Plan: Pro · 4 vCPU · 8 GB · 100 GB · $75/mo
Agent: Claude Code
Tabs: 2
Services: postgres:18 · redis:8
Runs: Around the clock, lid closed

Pro

Our pick for agent work

$75a month

5 agents plus the Docker services they test against

vCPU: 4
RAM: 8 GB
disk: 100 GB
Internet: 100 Mbit
Terminals at once: 5

Get my Compute

Questions about this

What if my laptop sleeps or loses Wi-Fi?

The run carries on. The agent works on your Compute; your laptop only showed the tab. Reopen the dashboard and you land in the same session.

What if my limit runs out mid-run?

The run carries on. With rotation on, it moves to your next subscription mid-task; with continue on, the agent types continue the minute the limit resets. The session keeps everything the agent has done so far.

Can the agent push to GitHub?

Yes. Put a deploy key or a scoped token in the project's home folder, as on any server; no other project's terminal can see it. The agent pushes branches the way you would.

What this job uses

More jobs people run