Where Does Tmuxp Store Session Files?
Tmuxp session workspace files in XDG, legacy and project-local spots.
Last updated
Tmuxp stores sessions as plain workspace files. The loader checks an env override first, then the XDG config dir, then a legacy dot folder. Project folders can carry their own file too.
Formats mix freely. YAML, JSON and Python all load the same way by basename or by path. There is nothing else to migrate beyond these files.
Where Tmuxp stores this, by platform
~/.config/tmuxp/[Session].yaml
Session workspaces in yaml, json or py formats, loaded by basename. Env override wins, then XDG, then legacy dot folder. Project-local files load by path. No daemon, cache or log file exists.
~/.config/tmuxp/[Session].yaml
Same XDG and legacy layout through pipx or Homebrew installs with POSIX paths.
Frequently asked questions
How do I back up Tmuxp sessions?
Copy your yaml or json session files out of the config dir with no session running. Project-local .tmuxp files travel with their repos. Restoring means putting the files back and loading one by basename to confirm.
Does Tmuxp keep a global config?
No. Tmuxp keeps no daemon, global config, cache or log file. Logging happens only on demand through an explicit log flag. Everything is a session file plus the loader.
Notice an outdated path? Let us know.