Where Does the Doppler CLI Store Config?
The Doppler CLI maps project folders to configs in .doppler.yaml, with login tokens in the OS keychain on Mac and Windows.
Last updated
Doppler keeps a per-user config file mapping directory scopes to projects, configs, and login state. On Unix it sits at ~/.doppler/.doppler.yaml; override the whole directory with DOPPLER_CONFIG_DIR. Tokens on Mac and Windows additionally live in the system keychain.
Scopes follow directory paths, not project names. Moving a folder orphans its entry, and a stale entry can later capture an unrelated new folder at the old path. Prefer doppler configure over hand-editing the YAML.
Where Doppler stores this, by platform
~/.doppler/.doppler.yaml
Scope-to-project mappings plus login state. Manage with doppler configure; hand edits risk stale scopes. Tokens may also sit in the OS keychain.
~/.doppler/.doppler.yaml
Same file and semantics as Linux. Login tokens additionally persist in the macOS keychain, which explains keyring sync errors after password changes.
%USERPROFILE%\.doppler\.doppler.yaml
Same file name under the user profile. Tokens additionally use Windows Credential Manager. DOPPLER_CONFIG_DIR relocates the directory on every OS.
Frequently asked questions
How do I reset Doppler CLI state completely?
Run doppler configure reset to wipe all scopes, then log in again and re-run doppler setup per project. Use this only as a last resort for wedged auth.
Doppler lost my project config after moving folders. Why?
You moved the project directory: scopes are path-based, so the old entry no longer matches. Run doppler setup again in the new location to rebind it.
Notice an outdated path? Let us know.