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.
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
There is no sandbox isolation or managed sandbox lifecycle. This provider supports only public networking and cannot enforce task resource limits. Registry images and startup commands are unsupported. Usesetup.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.