Skip to main content
Configure the lifecycle service through the host environment variables OPEN_SANDBOX_API_KEY and OPEN_SANDBOX_DOMAIN. The task image must support the execution service used by your OpenSandbox deployment.

​
Configure

​
Provider Params

Every provider accepts the common Environment schema plus its own declared provider options. Use the command below to list all accepted keys. Pass provider options alongside shared fields in --env-params or the flat YAML provider section. Image, resources, outbound policy, and environment variables retain their unified entry points; native aliases and unknown keys are rejected.
Use resources, run_resources, and evaluation_resources. Provider capabilities still differ: unsupported requirements fail explicitly, while storage limits follow the documented provider support policy. See Resource Limits.

​
Provider Behavior

The adapter manages the sandbox entrypoint internally and maps the shared build timeout to readiness waiting. Only the public network policy is supported; service-side network restrictions still apply. Use setup.workdir for the default command directory and setup.build_timeout_seconds for environment creation. The Benchmark selects the task workspace independently through its prepared input; neither setting replaces that workspace or an individual command timeout.