Skip to main content
Configure Daytona credentials in the host environment. The adapter reads DAYTONA_API_KEY; deployments can also use its existing DAYTONA_API_URL, DAYTONA_TARGET, DAYTONA_JWT_TOKEN, and DAYTONA_ORGANIZATION_ID environment settings.

​
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 maps setup.image to registry-image creation. It supports public, no-network, and allowlist policies with phase transitions. A custom startup command is not supported by this adapter. 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.