create_sandbox
Provision an isolated Docker sandbox with its own daemon, configurable CPU/memory limits, templates, and SSH access; use it to run coding agents and deploy compose stacks.
Instructions
Create sandbox HTTP POST /sandboxes
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "create_sandbox"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| cpus | No | CPU limit (cores). Default SANDBOX_CPUS; users up to SANDBOX_MAX_CPUS, the admin up to the host. | |
| name | No | Omit for a generated one (six letters and digits, k3x9q2): the name in the answer says which. GET /sandbox-name suggests one first. | |
| owner | No | Admin only: who the sandbox belongs to, someone who can sign in here. Omit for the caller. | |
| memory | No | Memory limit (512m, 4g). Default SANDBOX_MEMORY; users up to SANDBOX_MAX_MEMORY, the admin up to the host. | |
| runtime | No | How the sandbox runs (GET /runtimes). Omit for DEFAULT_RUNTIME (auto: sysbox where installed, else dind); kata where allowed (opt-in). | |
| ssh_keys | No | Extra SSH public keys for this sandbox only (your keys from /ssh-keys always get in) | |
| template | No | What runs inside (GET /templates). Omit for DEFAULT_TEMPLATE (starter). | |
| idle_timeout | No | Stop the sandbox after this long without HTTP traffic; the next request wakes it. Days are kept as hours (1d = 24h). 0 or off = never. Omit for template idle_timeout (default 30m). | |
| deep_sleep_after | No | Take the sandbox down (containers + network freed, data kept) after it has been stopped this long; the next request rebuilds it. "off" disables. Omit for template deep_sleep_after (default 7d). | |
| create_inner_stack | No | Whether to deploy the template's starter stack, as it is (it cannot be changed; deploy your own apps afterwards) |