Skip to content

Configuration

Settings use TOML. CLI flags override environment variables, which override configuration files.

Where configuration lives

Files merge in order; later values win:

Priority File
1 ~/.gdc/config.toml
2 $XDG_CONFIG_HOME/gdc/config.toml (usually ~/.config/gdc/config.toml)
3 <project>/.gdc/config.toml
gdc --config /path/to/config.toml print "<task>"

An explicit file replaces automatic discovery and fails on missing or invalid configuration. Automatic discovery warns and skips unreadable or malformed files.

A minimal config

[provider]
base_url = "http://localhost:11434/v1"
model = "qwen3.5:latest"

What overrides what

Setting CLI flag Environment
Endpoint --base-url GDC_BASE_URL
Model --model GDC_MODEL
API key --api-key GDC_API_KEY
Reasoning --reasoning GDC_REASONING
Config file --config GDC_CONFIG
Database --db-path GDC_DB_PATH
Session id --session-id GDC_SESSION_ID

The terminal's local server uses GDC_TUI_* options; remote mode uses server settings. See Environment variables.

Editing configuration

Method Use
Text editor Any TOML key
/config in TUI Provider, model, permissions and interface settings; Ctrl+S saves
gdc mcp commands Add, trust and remove server entries

What you can configure

Group Sections
Models and execution [provider], [agent], [task], [advisor], [roles], [[stream_rules]]
Permissions and data [permissions], [profile.<name>], [storage], [memory], [grants], [sandbox]
Extensions [mcp.servers.<name>], [plugin.plugins.<name>], [skills], [agents], [hooks]
Interface [tui], [output_styles]
Distributed execution [swarm]

See Reference for keys and Examples for configurations.