Where Does gomuks Store Sessions and Data?
Where gomuks keeps config, message store, and media cache on each OS, and the variables that relocate them.
Last updated
gomuks separates its world into config, data, cache, and logs under OS-standard roots. Config holds the listen setup and credentials, data holds messages and encryption keys, cache holds refetchable media. Environment variables relocate the whole tree or each piece.
The Electron desktop variant nests backends under its own session folder instead. Deleting data logs you out, while deleting cache only costs redownloads. That split is the entire backup policy in one sentence. Check the FAQ for per-backend details.
Where gomuks stores this, by platform
~/.config/gomuks
Config tree with connection settings; data and logs branch beside it under the same roots. GOMUKS_ROOT moves everything at once. Electron desktop instead uses its own session folder with per-backend subdirectories.
~/Library/Application Support/gomuks
Config and data together under Application Support with cache and logs in their macOS homes. Same environment overrides apply. The Electron desktop path differs; check its session folder for embedded backends.
%APPDATA%\gomuks
Config and data under Roaming AppData with cache and logs under Local. Variables relocate the same four trees. Deleting data here logs out exactly like elsewhere.
Frequently asked questions
how do I move gomuks to a new computer
Copy the config, data, and cache trees to the new machine at matching OS paths. The data tree holds keys and messages; losing it logs you out everywhere. Media cache can be skipped and refetched, since it is content addressed.
how do I relocate gomuks data
Set GOMUKS_ROOT to one folder for everything, or split with GOMUKS_CONFIG_HOME, GOMUKS_DATA_HOME, and GOMUKS_CACHE_HOME. Desktop clients embedding gomuks accept a root parameter with the same effect. Defaults follow each OS convention otherwise.
which gomuks folders need backup
Yes. Cache holds shared media safe to delete any time, while data holds keys and messages that logging out destroys. Config carries listen address and credentials. Back up data and config; ignore cache and logs.
Notice an outdated path? Let us know.