Skip to main content
Environments give harnesses a common execution surface: run commands, move files, create directories, expose a workspace, and release resources. A benchmark should describe what a task needs; the environment provider decides where it runs.

​
Provider Map

​
How Selection Works

Select the provider with --env:
Provider defaults live under environments.<provider> in config/defaults.yaml. Per-run overrides can be passed through --env-params.

​
Recipes And Remote Benchmarks

For heavy benchmarks, recipes usually infer provider-specific settings from task metadata: Do not pass image manually when a recipe can infer it. Manual image overrides are useful for custom tasks and debugging, but they reduce reproducibility for public benchmark runs.

​
Concurrency

--task-concurrency controls how many AgentCompass tasks are in flight for one run. runtime.provider_limits caps process-wide provider usage, so a high task concurrency value cannot exceed the provider limiter.