agental

Persistence

A stopped sandbox keeps its whole disk until you delete it, so your agent picks up where it left off.

StopStartDisk kept
Runningsandbox-01sbx_7f3e2a9c41d0b8e6
Stoppedsandbox-01sbx_7f3e2a9c41d0b8e6
Runningsandbox-01sbx_7f3e2a9c41d0b8e6
vCPU2
Memory4 GiB
Disk40 GiB
ImageUbuntu 24.04
RunningYour agent works, billed by the second. $0.027 / hour
StoppedFiles, packages and images kept. $0.0014 / hour
Running againSame ID, same disk, where it left off.

Stop it, and pick up where you left off.

Stop releases the machine and keeps the whole disk: files, packages, Docker images and build cache.

  • A stopped sandbox costs 5% of its running price, and is kept until you delete it.
  • Start brings back the same sandbox, under the same id. Stop it with its memory kept, for 10%, and every process comes back as it was.
  • A sandbox runs until you stop it, or until a time limit you give it, which you or an agent in it can move.
  • After 6 hours stopped it is archived, and a start still brings it back.
Read the sandbox lifecycle guide →
console · sandboxes
sandbox-01Runningsmall$0.027 / hourStop
research-agentStoppedsmalldisk kept · $0.0014 / hourStart
nightly-buildStoppedmediumdisk kept · $0.0027 / hourStart

Snapshot, roll back, fork.

Keep the disk as it is before a risky step, and go back to it if the step goes wrong.

  • A snapshot is of the whole disk, and the sandbox keeps running while it is taken.
  • Roll the same sandbox back, or start new sandboxes from a snapshot.
  • Fork a running sandbox to try two approaches from one state.
  • A snapshot is kept after its sandbox is deleted.
Read the snapshots guide →
sandbox-01 · snapshots
◷
before the migrationsnap_5c1d0a9e8b7f6e42 · 2 hours ago · 12 GiB
Roll backFork
◷
clean installsnap_a91e04c7d2b3f658 · yesterday · 8.4 GiB
Roll backFork

Make every sandbox the same way.

A template is what a sandbox is made as and held to: its size and what it starts from, the variables and files it gets, and what it may reach.

  • Every account has one named default, which a sandbox is on when you name none.
  • Secrets are read one at a time, and the console keeps them hidden until you ask.
  • A sandbox can have secrets of its own on top, used from its next command.
  • Tags and metadata every sandbox made from it has, changed for all of them at once.
  • A change reaches a sandbox when it next starts, or the running ones at once when you apply it. Nothing is restarted.
  • A template costs nothing. A sandbox is billed while it runs, and a little while it is stopped.
Read the templates guide →
template · ci-runner
Sizesmall
SecretsGITHUB_TOKEN kept out, NPM_TOKEN
Outboundgithub.com, registry.npmjs.org
Stops after4 hours