Sign in

AI agent sandbox that pauses with memory and runs past 24 hours

Updated

A sandbox for an AI agent that pauses with its memory and running processes, resumes on the next command, and, once the workspace has paid in, runs up to 7 days at a time, past E2B Pro's 24-hour sessions: the commands, the limits, and what it costs.

On this page14

A Prized sandbox is a Firecracker microVM that keeps an agent's state between sessions: pause it, and it keeps its memory, running processes and files, billed for storage only; the next command resumes it, usually in under a second. Once the workspace has paid in, it gets 24 hours by default, up to 7 days at a time; the clock stops while it is paused and starts again at each resume; you can extend it while it runs; and a paused one is kept until you delete it, though a move to a different kind of machine keeps only its files (Pause and resume). On the free credit, a sandbox gets 60 minutes of running in all and is kept 30 days after its last use (Free tier).

1. Create a sandbox that runs up to 7 days

Open Sandboxes to sign up and choose Create API key, then install the CLI and export the key in a new terminal:

curl -fsSL https://prized.dev/install.sh | sh
export PRIZED_API_KEY=dcp_…
ID=$(prized sandbox create --template prized-agent-v1 --max-runtime 7d --auto-pause 15m --label agent=support-bot)

--auto-pause 15m pauses it after 15 minutes with no command or file copy, so an idle agent costs no compute, and the label shows in prized sandbox ls. Over the API, the same create sends "maxRuntimeMin": 10080 and "autoPauseMin": 15 (Sandbox API: Create). --max-runtime 7d needs a workspace that has paid in (a plan or a top-up, from $10): on the free credit a sandbox runs 60 minutes in all, so leave it out there (Free tier).

2. Pause it with its memory, resume it with the next command

prized sandbox exec $ID -- 'nohup python3 -m http.server 8000 > server.log 2>&1 &'
prized sandbox exec $ID -- 'echo "step 1 done" >> notes.txt'

When the agent goes quiet the sandbox pauses on its own, or now with prized sandbox pause $ID. Days later, the next command resumes it first, with the server still running and the notes where they were:

prized sandbox exec $ID -- 'cat notes.txt && curl -s localhost:8000 > /dev/null && echo server up'

3. Keep it running past 7 days

Each resume starts a fresh 7 days of run time, so a sandbox that pauses at least once a week never runs out. Busy for more than 7 days straight? Extend it while it runs; it stops at 7 days from now, so extend again later (Run time):

prized sandbox extend $ID --by 2d

Past E2B Pro's 24-hour sessions

E2BPrized
Longest run without a pause1 hour on Hobby; 24 hours on Pro, at $150 a month plus usage; multi-day sessions on Enterprise7 days at a time once the workspace has paid in, 24 hours by default, extendable; 60 minutes of running in all on the free tier
A pauseKeeps memory, processes and files until you delete it; a resume resets the limitKeeps memory, processes and files until you delete it (30 days after last use on the free tier), or only the files after a move to a different kind of machine; once paid in, a resume restarts the clock

Daytona has no run time limit, only an idle auto-stop you can turn off; its sandboxes are containers by default, which cannot pause; its VM sandboxes pause with memory and fork. Modal, Vercel Sandbox and the rest: E2B alternatives.

What to know

  • Paused state lives on one machine. If that machine fails, the sandbox goes to error and what it held is lost: push work to git or copy it out as you go (Pause and resume).
  • Time inside it after a long pause. Its wall clock is right after a resume, but its monotonic time missed most of the pause: renew tokens, leases and locks when it resumes (Clocks inside the sandbox).
  • Deleting erases it, by hand, by --auto-delete, or at the end of its run time.
  • On the free credit, a paused sandbox is kept 30 days after its last use; once the workspace has paid in, until you delete it (Paused retention).
  • Needs Docker? Create the sandbox from prized-docker-v1, on a workspace that has paid in (Run Docker and Compose in a sandbox).
  • Needs sudo or months on one machine? Use a box: a Linux machine with sudo and no maximum run time (Persistent cloud computer).

What it costs

4 vCPU, 8 GB (the default)
Running, per hour$0.261
Working 2 hours a day for 30 days$15.66
PausedNo compute: its disk and memory count as paused storage, and a workspace's first 20 GB are included

Each session also runs up to 15 idle minutes before --auto-pause pauses it. This shape holds 18 GB paused, inside the included 20 GB; past them, paused storage is $0.05 per GB-month (Billing: Sandboxes).

Common questions

What is a sandbox for an AI agent?

An isolated machine where an agent runs the code it writes, away from your computer and your data. A Prized sandbox is a Firecracker microVM with its own kernel that your code creates, pauses, forks and deletes through the API or prized sandbox (Sandboxes).

Can a sandbox pause and keep its memory?

Yes: a pause saves its memory and disk, and on resume every process carries on where it stopped, a server it started included; after a move to a different kind of machine, the sandbox keeps only its disk and starts fresh (Pause and resume).

Can a sandbox run longer than 24 hours?

Yes, on a workspace that has paid in: create it with --max-runtime (maxRuntimeMin) up to 7 days, and extend it again while it runs. A custom plan has no maximum.

Does pausing reset the run time?

Yes, once the workspace has paid in: no clock runs while it is paused, and each resume gives it its full run time again. On the free tier a resume carries on the time left instead (Run time).

What happens when the run time ends?

The sandbox is deleted, its disk and memory with it, and there is no undo (Automatic pause and delete). Pause it before then (or, once the workspace has paid in, extend it), and copy out what you need.

Can I try it for free?

Sign-up comes with $30 of free credit, once per person, and no card. On it, sandboxes run within the free tier, each up to 2 vCPU, 4 GB and 60 minutes of running in all; after a top-up or a plan, new sandboxes get 24 hours by default, up to 7 days.

Sources

E2B and Daytona checked November 3, 2026: E2B pricing (session length per plan) and persistence (pause and resume); Daytona sandboxes (containers, VM sandboxes, auto-stop).