Today we're introducing Cloud Sandboxes: same microVM isolation as Docker Sandboxes on your laptop, same CLI, always-on Docker-managed compute. Close your laptop. Keep the agent running. Move between local and cloud with one command. $250 credit for new accounts:

brb, telling my agents to update

This feels like another sign that coding agents are becoming workloads, not just developer tools. Once tasks run for hours autonomously, isolation, reproducibility and where the agent runs start becoming part of the stack. The next interesting problem is credentials: how do we give these long-running agents enough access to actually work, without giving them too much?

Meh....never going to stop container escape

Close your laptop, keep the agent running. That does a lot of work for seven words. Congrats on the launch, this one solves a real annoyance.

microvm isolation contains the agent, it doesn't authorise it; an always-on sandbox in someone else's cloud still holds your credentials, and a closed laptop means nobody watching the egress who reviews what the agent sends when it decides on its own?