Configuration

Configuration

The CLI reads configuration from ~/.agent/config.yaml by default. You can override this with the --config flag.

Profiles

Use profiles to switch between workspaces or accounts. Define them in your config file under the profiles key and activate with --profile.

Environment Variables

Any config value can be overridden with an environment variable prefixed with AGENT_. For example, AGENT_API_KEY overrides the api_key config value.

Config file location

The CLI reads global config from ~/.queue/config.yaml. Per-project config lives in queue.yaml at your project root. Project config takes precedence over global config.

Global config structure

default_workspace: my-workspace default_model: claude-3-7-sonnet api_key: qk_live_xxx # or use QUEUE_API_KEY env var output_format: text # text | json telemetry: true

Profiles

Profiles let you switch between workspaces, accounts, or environments without changing environment variables or editing your config:

profiles: work: api_key: qk_live_work_xxx default_workspace: acme-engineering personal: api_key: qk_live_personal_xxx default_workspace: my-projects

Activate a profile with queue --profile work run my-agent “…” or set the active profile permanently with queue config set profile work.

Environment variables

Any config key can be overridden with an environment variable prefixed with QUEUE_. Keys are uppercased and dots replaced with underscores. For example, QUEUE_DEFAULT_MODEL overrides default_model.

Per-project config

Define agents in queue.yaml at your project root. This file is checked into your repo and shared with your team:

agents: refactor-agent: model: claude-3-7-sonnet max_steps: 30 system_prompt: | You are a TypeScript engineer. Refactor code for clarity and correctness. tools: [read_file, write_file, run_command, search_codebase]