The Sandbox VM Primer

When you let an AI agent write and run code, that code often executes on your actual computer — the same one holding your photos, your saved passwords, your client work. The AI is usually right. But 'usually' is the problem. It can delete the wrong folder because a path was slightly off. It can install a package that turns out to be malicious. It can run a command no human ever read before it executed. None of this needs the AI to be 'evil' — it just needs to be confidently wrong once, while pointed at your real file system.

The fix isn't to make the AI smarter or to babysit every command. It's to stop the AI from ever touching your real machine in the first place. Instead, you give it a separate, sealed-off computer to work in. It does everything in there — installs, deletes, experiments, mistakes and all. Your real machine sits behind a wall and never sees any of it. That sealed-off computer is what the rest of this primer is about.

Picture a brand-new, empty computer that appears on demand in a fraction of a second, does one job, then vanishes completely — taking everything that happened inside it along with it. Nothing it changed survives. Next time you need one, you get a fresh, clean one again. That's a disposable (or 'ephemeral') machine. Because it's thrown away after each job, a mistake inside it has nowhere to go. There's no real file system to damage and no second session for anything nasty to linger into.

Think about a rental car. You'll drive it harder than your own. If it gets a scratch, you shrug — it isn't yours, and you hand it back at the end. Now imagine your AI gets the rental, and you keep your own car safe in the garage. The AI can push the rental to its limit, make a mess, even crash it — and your own car never gets a scratch. A disposable computer is the rental. Your laptop is the car in the garage. That's the whole idea: let the AI be bold somewhere that doesn't matter, so it never has to be careful somewhere that does.

This disposable computer has a proper name: a sandbox VM. 'Sandbox' is the old software word for a safe, walled-off play area where nothing you do can escape into the real system. 'VM' is short for virtual machine — literally a whole computer running as software inside another computer. Put together, a sandbox VM is a self-contained computer-inside-your-computer that runs the AI's code in isolation and then gets wiped. Two words, one habit: the AI works in the sandbox; your real machine stays out of reach.

This isn't a fringe trick. Developers have run code in disposable, isolated environments for years — it's how large platforms safely run code from millions of strangers at once. What's changed in 2026 is that AI agents made the problem everyone's problem: now ordinary people, not just engineers, are letting software write and execute real code on their machines. In response, multiple independent platforms have converged on the same answer — fast-booting, throwaway, isolated machines for agent code. When separate teams independently land on the same design, that's usually a sign it's becoming the baseline rather than a nice-to-have.

You don't need to build any of this yourself — you need to recognise it. When an AI coding tool tells you it runs code, look for three things. One: isolation — the code runs in its own sealed environment, not directly on your machine. Two: it's disposable — the environment is fresh each time and discarded after, so nothing carries over. Three: your real files only go in if you explicitly put them there. A tool that ticks those three boxes is giving the AI a rental car. A tool that runs commands straight on your laptop is handing it your own keys. Knowing the difference is the entire point of this primer.