01
Use JSON or JSONC with the published schema.
The schema powers validation and editor completion. JSONC comments and trailing commas are supported.
brokencode.json
{
"$schema": "https://brokengpt.com/config.json",
"autoupdate": true
}02
Configuration layers merge from broad to specific.
- Remote organization defaults, when configured.
- User config at ~/.config/brokencode/brokencode.json.
- A custom path supplied through BROKENCODE_CONFIG.
- Project brokencode.json files from the repository root toward the current directory.
- .brokencode directories containing agents, commands, plugins, skills, tools, and themes.
03
Environment variables support automation and managed environments.
- BROKENCODE_CONFIG points to an explicit config file.
- BROKENCODE_CONFIG_DIR adds a custom configuration directory.
- Keep credentials in the operating system keychain or environment rather than committing them.
Check your file
brokencode --config ./brokencode.json