Sandbox providers
Configure Docker, Daytona, or Lambda execution and their required fields.
The sandbox is the isolated environment where the agent inspects repositories and produces output. The worker remains the trusted controller.
Docker
Docker uses the bundled runtime image by default. Set image, cpus, memory, or pids_limit only to override the displayed defaults.
{
"image": "tasuku-agent-runtime:local",
"cpus": "2",
"memory": "4g",
"pids_limit": 512
}The bundled adapter drops capabilities, uses no-new-privileges, enforces resource limits, mounts a read-only root filesystem, and uses temporary filesystems. The worker's Docker access is still privileged operator infrastructure.
Operator-controlled Docker boundary
Docker host selection is intentionally not a repository setting. Configure the worker's Docker endpoint with DOCKER_HOST. Agent containers use the Docker host's default outbound network. The dashboard exposes only per-sandbox resource settings.
Daytona
Daytona requires only an api_key reference. API URL, target, image, resource limits, auto-stop, and ephemeral workspace behavior fall back to the defaults shown in the dashboard when omitted.
{
"api_url": "https://app.daytona.io/api",
"api_key": "${secrets.DAYTONA_API_KEY}",
"image": "tasuku-agent-runtime:latest",
"target": "us"
}Store the API key as an instance or repository secret; do not embed plaintext in reusable configuration. Configure outbound controls in the Daytona environment when your deployment requires them.
AWS Lambda
AWS Lambda remains supported for existing API configurations but is temporarily unavailable as a new dashboard selection.
Lambda requires function_name and region. The function must use Tasuku's Lambda agent runtime contract and return its typed event batch.
{
"function_name": "tasuku-agent-runtime",
"region": "us-east-1"
}Configure VPC routing and outbound controls on the Lambda function when your deployment requires them.
Shared expectations
Every provider must make the agent toolchain available, isolate the agent from control-plane resources, enforce appropriate resource limits, and return bounded output to the worker. Codex runs with its workspace sandbox and automatic approval review; Tasuku does not maintain a separate destination allowlist. Changing providers does not move the GitHub publication boundary into the sandbox.