Where Does Claude Code Router Store Config?
Claude Code Router keeps its config in a SQLite database in home. Paths for Windows, macOS, Linux and Docker.
Last updated
Claude Code Router does not use a plain config file anymore. Current builds keep everything in a SQLite database called config.sqlite inside a dotfolder in home. The desktop UI and Settings export are the supported ways to change it.
Older guides naming a config.json describe the legacy path. That file is read exactly once as a migration source when no database exists, then ignored. After migration, editing the JSON does nothing. Do not edit the SQLite file while the router runs; companion WAL files sit beside it.
Where Claude Code Router stores this, by platform
%APPDATA%\claude-code-router\config.sqlite
For example C:\Users\<you>\AppData\Roaming\claude-code-router\config.sqlite. Use the Desktop UI or Settings backup export to edit. A legacy config.json migrates once, then stays ignored.
~/.claude-code-router/config.sqlite
Same SQLite store as Linux. Companion config.sqlite-wal and config.sqlite-shm appear beside it while running. Stop the router before copying the folder for backup.
~/.claude-code-router/config.sqlite
Docker setups use /data/.claude-code-router/config.sqlite with HOME set to /data, so persist the whole /data volume. Editing the live database by hand risks a corrupt config; prefer the UI.
Frequently asked questions
Where is the Claude Code Router config file?
There is no live config file. Current builds store settings in config.sqlite under ~/.claude-code-router on Mac and Linux, or %APPDATA%\claude-code-router on Windows. Change it through the Desktop UI or export a backup from Settings.
Can I still edit config.json?
Only for a one time migration. When no SQLite database exists, the router imports config.json once and then never reads it again. After that point the JSON is dead weight, so delete it to avoid confusion about which file is real.
How do I back up my router setup?
Stop the router, then copy the whole .claude-code-router folder with its SQLite files. The Settings page also offers an export. Keep provider keys out of shared backups, since the database holds secrets in plain form.
Notice an outdated path? Let us know.