Configuration
Where config, keys and data live, and which layer wins when they disagree.
Later layers win: flags, then the project's .zerd/config.toml, then the user config, then defaults.
| What | Where |
|---|---|
| Keys | environment variables, or zerd's own .env (/connect <provider> saves one). API_KEY and BASE_URL set the default gateway |
| User config | ~/Library/Application Support/zerd/config.toml (Linux: ~/.local/share/zerd, Windows: %APPDATA%\zerd) |
| Project config | .zerd/config.toml in the repo (sensitive keys need --trust) |
| Data | sessions, traces, transcripts, lessons and review memory in the same user folder; ZERD_DATA_DIR moves all of it |
| Project instructions | AGENTS.md / CLAUDE.md in the repo, read automatically |
Useful flags: -m <model>, --approval on-request|auto-edit|auto|plan|yolo, --effort low|medium|high, --trust,
--add-dir <path>, --challenge, --pi / --no-pi, -c <dir>.