Persistent shells for coding agents
Close the lid. It keeps building.
Somewhere out there, a machine is still working on it. Put the iPad down mid-task; nothing stops. Pick it up tomorrow and the session is exactly where you left it.
The shape of it
-
01
A machine, not a container
Yours, with a name and a disk that stays written to. About three minutes from claim to shell, toolchain already on it.
-
02
The work outlives the connection
Agents run on the box, so closing the lid closes nothing. What was running is still running.
-
03
It stands down when you do
An idle box sleeps and wakes with your files exactly where you left them. You do not pay for a machine to sit warm overnight.
-
04
Keys stay out of your dotfiles
Secrets are sealed on the server and granted to a box — global, per workspace, or per machine. Revoke one and the box loses it on the next read.
The desktop side already exists and is free: Asylum races several coding agents at the same task, each in its own worktree, and lets you merge whichever one won. Take it now — Devpipe is what it reaches for when your laptop is not enough.
There is more here than a box with a shell on it. That part is easier to show than to describe, and it is close.
Claim your username
Names are first come, and yours becomes the address your machines answer on. We will write once, when there is something to log into.