Finishing a box
How to end work on a box: sandbox_review when the person should try the result, sandbox_stop when there is nothing to see, and what each leaves behind.
Finish every box you start before you stop working on it:
- Use
sandbox_reviewwhen the person should try a running app. The box appears under Ready for you immediately, and the call waits for feedback or completion within the client's supported limit: up to 25 seconds for undeclared clients, or up to 30 minutes with long-wait configuration. Read the returned report before continuing; after timeout, resume withreviewId, or read a known report again withsandbox_report. If the box later stops, screenshots and recordings from the last seven days remain available under All sandboxes → Stopped; the box and/workare gone. A box waiting for review still freezes and is stopped by the usual idle rules (Box states); the person opening the review wakes a frozen box, and a stopped one has to be handed over again on a new box. Name what they open withopen:webwith the port the page is served on, orboxfor the box's screen. If aboxreview fails because nothing is on the screen, start the app on the box's display or on a device, then try again. - Use
sandbox_stopwhen there is no running app for the person to try. The box stops, while screenshots and recordings remain available until seven days after capture in the app’s Stopped list. Download anything needed from/workfirst.
A box left running without either shows in the person's app as AI stopped (below) and waits for them to decide what happens to it. A conversation can also end before it gets to either (a laptop shut, a client closed), so commit your work in /work as you go, with messages that say what is done and what is left, and push it or sandbox_pull it when it matters: steps[] records what was run, not the files. The MCP server's instructions say the same to every client: give every sandbox_start a goal, finish every box with sandbox_review or sandbox_stop, and read sandbox_status before picking up a box another conversation left.
What a box leaves, and who can still see it once the box is stopped (details in the sections linked):
| What | Deleted | Before the box is stopped | After it is stopped |
|---|---|---|---|
Screenshots and recordings from steps and from sandbox_shot (sandbox_exec, sandbox_shot) |
Seven days after each capture | Screenshots & recordings in the app and GET /v1/boxes/{id}/media |
All sandboxes → Stopped (last 7 days) and /media, until each expires |
Files fetched with sandbox_get, including fetched recordings (sandbox_get) |
Automatically removed after about one day; not counted as stored files. URLs last one hour | Request a fresh URL while the box exists, or download directly with sandbox_pull |
Only URLs still valid; no new URL can be requested |
Frozen box posterUrl and sandbox_review card picture: only the newest of each is kept, replacing older pictures (Credits) |
With the account; currently no individual deletion in the app | The app shows the latest pictures | The Stopped list and GET /v1/boxes?all=1 can show the latest poster |
A recording stopped for you that you have not fetched (sandbox_shot) |
With /work |
You, with sandbox_get; it is not in the app or in /media |
Gone |
/work |
When the box is stopped | You, with sandbox_exec, sandbox_get and sandbox_pull |
Gone |
Every tool and topic is listed in the tool reference.