Where Does the PlanetScale CLI Store Its Config?
Where the pscale CLI keeps its config file, API endpoint and login tokens on Windows, macOS and Linux, and how to reset it.
Last updated
The pscale CLI reads one YAML file for API endpoint, tokens and output defaults. Interactive logins write there. Flags and env vars override it per invocation without touching disk. The file stays small, but it controls auth for every command that runs without explicit flags. A missing or stale entry shows up as failed calls rather than a clear path error.
The default sits in your XDG config home on all three OSes. Service tokens belong in CI secrets, not in this file on a shared runner. A stale token here produces auth errors that look like API outages. Delete the file with the CLI logged out to force a clean login, and keep a custom path in mind when a per run flag was ever used.
Where PlanetScale CLI stores this, by platform
%USERPROFILE%\.config\planetscale\pscale.yml
Default pscale.yml with API token and endpoint. Override per run with --config. Delete it to force a clean login.
~/.config/planetscale/pscale.yml
Same XDG relative path on Mac. Homebrew installs share it with manual installs, so one login covers both.
~/.config/planetscale/pscale.yml
Respects $HOME on servers and containers. Mount only this file into Docker, not your whole .config, when aliasing pscale through a container.
Frequently asked questions
How do I log the PlanetScale CLI out completely?
Delete the config file while logged out, then run pscale auth login again. Service tokens passed via flags never touch the file. Check for a custom path first if --config was ever used.
Can I use a different pscale config per project?
Pass --config with an explicit path. CI jobs usually inject tokens via env vars or flags instead of writing the file at all. The default path stays for interactive use.
Notice an outdated path? Let us know.