ai-blackteam uses a YAML config file with environment variable fallbacks. Most things work out of the box - you just need to set API keys.

Config File Location

Created automatically on first use. Override with --config or by passing a path to load_config().

Full Default Config

This is what ai-blackteam uses when no config file exists:

Setting Values

CLI

Python

Direct YAML Edit

Environment Variables

API Keys

Environment variables take precedence over null config values. ai-blackteam checks for {PROVIDER_NAME_UPPER}_API_KEY: Ollama doesn’t need an API key.

Config File References

You can reference environment variables in the config file:
The ${VAR_NAME} syntax is resolved when config is loaded.

Config Resolution Order

  1. Default config (hardcoded)
  2. Config file (~/.ai-blackteam/config.yaml) - merged on top
  3. Environment variables - fill in null API keys
For API keys specifically:
  • If the config file has a non-null value, that’s used
  • If the config value is null, ai-blackteam checks the environment variable
  • If neither exists, the provider will fail with an auth error

Viewing Current Config

Displays the resolved config with API keys truncated (first 8 chars + ...).

Deep Merge

User config is deep-merged with defaults. This means you only need to specify what you want to change:

Files and Directories

Source

src/ai-blackteam/config.py