Skip to main content
AgentCompass defaults live in code. Config files are override layers; CLI flags, Python keyword arguments, and per-run JSON params override all config files.
Use environment variables or private --config files for secrets. Run agentcompass config show to inspect the effective merged config and agentcompass config docs <kind> <id> to inspect component fields.

Config Command

agentcompass config show prints YAML by default. Without component selectors it prints the global runtime and execution sections. Add --benchmark, --harness, and --env for the component defaults you want included in an editable run template:
User-level defaults are loaded from ~/.config/agentcompass/config.yaml; project-level defaults are loaded from <repo-root>/config.yaml; run-specific files can be passed with repeatable --config flags. Use agentcompass config docs <kind> <component-id> to inspect one component’s fields:

Override Order

  1. Built-in runtime, execution, and component defaults.
  2. ~/.config/agentcompass/config.yaml.
  3. <repo-root>/config.yaml.
  4. Explicit --config / config_path files, in order.
  5. CLI flags, Python keyword arguments, --benchmark-params, --harness-params, and --env-params.
  6. Recipe rewrites from task metadata before environment startup.

Runtime

Execution And Analysis

Environments

Host Process

Docker

Brain++

PCluster

HBox

Daytona

Benchmarks

Harnesses

Coding Harnesses

Research And Tool Harnesses

Terminal, GUI, And Code-Interpreter Harnesses

Secrets

Prefer environment variables for secrets. Model endpoints can use MODEL_BASE_URL and MODEL_API_KEY; Modal can use MODAL_TOKEN_ID and MODAL_TOKEN_SECRET; Daytona can use DAYTONA_API_KEY.