Where Does the Argo CD CLI Store Logins?
The argocd CLI keeps server logins and tokens in a config file under .config/argocd in your home folder.
Last updated
The argocd command remembers servers in a config file under .config/argocd in your home directory. Each login adds a server entry with its token and TLS preference. Contexts switch between instances the way kubectl contexts do.
Server side state lives in the cluster, not in this file. Deleting it only logs you out locally. Tokens inside expire with the server session policy, so stale entries fail cleanly rather than dangerously.
Where Argo CD stores this, by platform
~/.config/argocd/config
Server entries with tokens per context. Manage with argocd login and argocd context commands. Deleting the file logs out everywhere locally.
~/.config/argocd/config
Same XDG layout on Mac regardless of install method. Homebrew installs do not relocate it. Tokens refresh on next login.
C:\Users\[username]\.config\argocd\config
Same relative layout under your profile. Exact Windows handling has varied by release, so confirm the file exists after first login.
Frequently asked questions
How do I switch Argo CD servers?
Use argocd context to list and switch stored servers. Each entry keeps its own token. Log in again when a token expires.
Does deleting the file affect the cluster?
No. It only clears local logins and contexts. Applications keep syncing server side. Log back in to resume managing them.
Notice an outdated path? Let us know.