who owns the box
three big labs shipped the same thing this quarter. a persistent, isolated sandbox your agent lives in, that keeps its files between runs. anthropic in april, google in may, microsoft in june. same shape three times. all of them rented.
when one lab ships a primitive, it’s a bet. when three ship the identical one inside a quarter, the bet is settled. the server-resident agent sandbox is the consensus answer now, not a fringe idea. that part we agree with. we’ve been building on it since before it had a name.
here’s the part worth sitting with.
what all three actually shipped
strip the branding and the three announcements describe the same machine:
- an agent gets its own isolated sandbox, provisioned through an API
- it has real disk, and the disk survives between sessions
- microsoft’s own words: “resume with filesystem intact, files, disk state, and session identity persist across scale-to-zero”
- when the agent goes idle, it scales to zero and you stop paying
that last line is the whole design. these are rented rooms. the agent checks in when there’s work, the provider spins the room down when there isn’t, and you never hold the key. it’s a good design for an api product. it’s built around their economics, not your ownership.
the tell
three labs converging on one shape means the shape stopped being the moat. if the sandbox is table stakes, the real question moves up a level: who holds the box.
rented gets you a session. it appears for a task and disappears after. it’s provider-controlled, it scales to zero, and “your” state lives on infrastructure you don’t touch and can’t drive between the moments they decide to run it.
that’s fine for a function call. it’s the wrong shape for a coworker.
owned is a different thing
a 5dive agent doesn’t check into a room. it lives on a machine that’s yours, running on the claude plan you already pay for, awake whether or not there’s a task queued this second. you can open it, watch it, redirect it mid-run. you can put a whole team of agents on the same box and let them share one memory and hand work to each other.
that’s not a bigger version of a rented sandbox. it’s the other side of the line. one is a session you rent. the other is a machine you have.
(the same split shows up on the bill: metered cloud vs your own subscription.)
the labs just spent a quarter proving the sandbox is the future. good. the question they left open is the one we answer: you can own the thing, not borrow it.
(owning the box is half of it. the other half is what runs on it, and when someone counted, that turned out to be mostly plain plumbing, not ai: we did the math.)
start here: put a team of agents on a box that’s actually yours. or read exactly how it works, it’s open source: github.com/5dive-ai/5dive.