Overview
Features
Isolated Node.js sandbox containers
Start and manage isolated Node.js sandbox containers for each job, ensuring environment isolation and reproducibility.
Execute shell commands inside containers
Run arbitrary shell commands within the sandbox to interact with the runtime environment.
Per-job npm dependency installation
Install specified npm dependencies per job before script execution.
ES Module support and stdout capture
Run ES module JavaScript snippets and capture stdout for results.
Tear down containers cleanly
Automatically remove containers after execution (with an option for detached mode to keep them alive).
Detached mode for long-running services
Keep the sandbox container running after script execution to support long-lived servers.
Ephemeral usage (no persistent storage)
Operate with ephemeral containers and no mandatory host storage by default.
Return files and outputs to host
If scripts save files, return stdout and any created files (including images) to the host via the configured files directory.
Who Is This For?
- Developers:Run JS in isolated sandboxes with on-the-fly npm installs for experiments.
- AI engineers:Execute code via MCP clients (Claude, VS Code) in ephemeral containers for experiments.
- Educators:Demonstrate code execution and npm installs in reproducible sandboxes for teaching.




