your code stays yours

The most common question we get is the most important one: what happens to my code?

Two answers, and they don't conflict: we keep it safe, and we keep it yours.

Safe: we don't lose your work

When you start an agent, a sandbox boots and your code lives on its local disk while you work. Containers pause when they're idle to save you money, and they can be evicted or restarted. So we continuously snapshot your /workspace — encrypted at rest and in transit — to private object storage, and restore it the instant you come back.

Snapshots happen in the background while you work. You don't request them. You don't wait for them. If the container restarts, your files are back before the shell prompt returns.

That means a project you started from scratch and haven't pushed to GitHub yet survives an idle pause, a restart, or an eviction. Losing that work used to be possible. It isn't anymore.

Yours: we don't hold it hostage

Persisting your code is not the same as owning it.

• We never sell, share, or rent your code.
• We never train models on it.
• We never use it to improve our own systems.
• GitHub stays your source of truth — publish a workspace to a repo whenever you're ready.
• When you destroy an agent or delete your account, its workspace and every snapshot are destroyed with it.

You can export your workspace at any time. You can delete it at any time. There is no lock-in, no proprietary format, no "contact sales" to get your own files back.

What the wrong default looks like

Some platforms keep your code indefinitely, train on it, or make deletion a support ticket. We chose the opposite default because most builders' code is their leverage. The job is to keep it safe enough that you never lose a day's work, and private enough that you never think twice about whose hands it's in.

Durable, encrypted, never resold, gone when you say so — that's the bar.

The full picture

If you want the line-by-line detail, the security model and data and retention pages spell out exactly what happens, storage region by storage region, action by action.