StateSet Sandboxes
A sandbox is an isolated runtime an agent executes inside. It gets controlled access to tools and data, its output streams back for audit, and it disappears when you’re done. This is where you run agent code you don’t want touching your infrastructure directly.The lifecycle
Files
POST /api/v1/sandbox/:id/files/write and /files/read move data in and out without going through
a shell command.
Why isolation matters
An agent that can execute code is, by construction, an agent that can execute the wrong code. A sandbox bounds the consequences: a bad run wastes a container and a timeout rather than reaching your systems.Always stop explicitly
timeout_seconds. The finally block is the difference
between a failed run and an expensive one.
Where sandboxes are used
They back agent execution for ResponseCX, the Console, and iCommerce agent workflows.Next
Quickstart
First sandbox, end to end.
API reference
Every endpoint.
Architecture
Controller, runtime, isolation model.
Security
Isolation guarantees and hardening.