Where Does Telepresence Store Config and Cache?
Telepresence keeps cluster login state and per-user config in your home directory, with logs beside them. Folders for each OS are inside.
Last updated
Telepresence stores its state per user, not per project. Connection and daemon state, cluster credentials, and config files sit in a telepresence folder inside your home directory, while logs accumulate in a cache folder nearby.
That layout decides two habits. Back up nothing here for disaster recovery; credentials expire anyway. To fix weird state, quit the daemon and clear the folders rather than reinstalling the binary, then reconnect and let them rebuild.
Where Telepresence stores this, by platform
~/.config/telepresence
Config, daemon state, and cluster credentials. Logs sit in ~/.cache/telepresence beside it. Honors XDG_CONFIG_HOME when set.
~/.config/telepresence
Same Unix-style layout as Linux, not the Application Support tree. Clear both config and cache folders when the daemon wedges.
%APPDATA%\telepresence
Config and state in Roaming AppData. Logs land nearby under the same vendor folder; check the Traffic Manager output first for cluster-side errors.
Frequently asked questions
How do I reset Telepresence login state?
Run telepresence quit, then log out and delete the config folder for your OS. Next connect starts clean and re-prompts for cluster credentials.
Where are Telepresence logs?
Check the cache folder next to the config on Linux and macOS, or the Logs area under AppData on Windows. Verbose flags on the connect command add detail.
Notice an outdated path? Let us know.