Where Does Qoder Store Settings?
The Qoder user settings file, the project level overrides next to it, and the variable that moves the config folder.
Last updated
Qoder CLI reads three settings files and merges them in a fixed order. Your personal file lives at ~/.qoder/settings.json and follows you across every project. Each project can add its own .qoder/settings.json for shared conventions plus a settings.local.json for private machine overrides.
The layout is identical on Windows, macOS, and Linux, which keeps dotfile setups simple. One environment variable, QODER_CONFIG_DIR, relocates the whole user directory when the default home location does not suit you. Inside the app, the /settings command shows the merged result.
Where Qoder stores this, by platform
%USERPROFILE%\.qoder\settings.json
Same file as the other platforms, under your user profile. Personal themes, default models, and UI taste go here. Project files in the current repo override it, and the QODER_CONFIG_DIR variable can point this whole directory elsewhere.
~/.qoder/settings.json
The user level file for personal preferences across all projects. Team conventions live in the project root .qoder/settings.json instead, which is committed to version control. Local secrets go in settings.local.json beside it.
~/.qoder/settings.json
Identical layout to macOS. If Qoder ignores project settings here, check directory trust: untrusted working directories load only the user level file. Approve the trust prompt or pin the directory in permissions.trustDirectories.
Frequently asked questions
where do I put personal vs team Qoder settings
Put personal taste in ~/.qoder/settings.json and team rules in the project .qoder/settings.json file that gets committed. Machine specific secrets belong in settings.local.json, which stays uncommitted. The merge order is built-in defaults, then user, project, local, and command line flags last.
how do I move the Qoder config directory
Set QODER_CONFIG_DIR to the folder you want before launching Qoder, and the user level settings, auth state, and plugins follow it there. Project level .qoder directories always stay at the project root regardless of this variable.
why is my Qoder settings change not applied
Some entries only apply after a restart, which the reference marks per item. Others, like project trust decisions, are ignored when the working directory is untrusted. Run /settings inside Qoder to see the effective values before chasing a typo.
Notice an outdated path? Let us know.