Use Sandbox for isolated code, stateful Python cells, supervised agent workers, and files.
Begin with a provisioned controller and credentials or the separate local Docker developer
backend. A documentation URL does not provision runtime capacity.
Start with a result
Keep the correct state
Sandbox lifetime, process runtime, caller wait, session budget, and provider billing are
separate. Startup consumes lifetime. A command receipt can outlive a connection; a process
can outlive its start request. Unknown outcomes stay unknown until reconciled.
Durable /workspace storage can preserve files across supported recovery/pause, but not
RAM or sockets. Managed workspace deletion follows sandbox termination. Export retained
artifacts and verify result bundles before that identity expires.
Review the deployed contract
The October 20 source includes controller/SDK 2.12.0 candidate and CLI 3.3.0 work, separately
from hosted v2.10.1 inventory. New server task registry and shared tunnel features require
their migrations/capabilities. Source tests and package installs do not deploy those changes.
Continue with product scope,
runtime boundaries, and
operations evidence. Last modified on October 20, 2026
