Summary
Code that runs somewhere it cannot hurt you.
The container is addressable and reusable, so a session installs what it needs once and keeps working in the same place — and whatever it produces comes back as a file you can open.
What it is
An isolated execution environment. Each sandbox is a Docker container with an ID; code and terminal commands run inside it, packages install into it, files upload into it, and generated files come back as web links.
What you get
- A sandbox created as a Docker container, and existing ones listed for reuse
- Python code executed inside a named sandbox
- Terminal commands run in the same container
- Packages installed into a sandbox, with the install status checked afterwards
- Files uploaded into a sandbox to work on
- Generated files reachable over web links, with a built-in web interface for watching results
Requirements
Docker on the host, Python and uv. It serves SSE at http://127.0.0.1:8181/sse, bound to localhost — change the host in config.toml to expose it, and turn on the optional API-key authentication if you do.