8000
Question: After update my saved session did not load anymore. Is there a way how to make it survive the update? · Issue #35 · amirlehmam/wmux · GitHub
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Question: After update my saved session did not load anymore. Is there a way how to make it survive the update? #35
Fixed in v0.9.0 🚀 Thanks @foschmitz — and sorry for the lost session.
Root cause: on every version update, wmux ran a handleVersionChange() that deliberately deleted all session data — including your explicitly named saved sessions — to avoid stale state freezing terminals. That was too aggressive: named sessions are layout-only snapshots (no live PTY handles), and loading one always re-spawns fresh shells (pty.create when pty.has(surfaceId) is false), so there's nothing stale to freeze.
Now the version-change reset touches only the volatile auto-session (session.json); your named saved sessions and the last-session pointer are preserved across updates. Added two unit tests to lock this in.
One honest caveat: live processes still can't survive an app restart (the OS kills them when wmux exits). "Restoring a session" reopens the layout — workspaces, panes, tabs, and each terminal's last cwd (issue #20) — and starts fresh shells there; it does not resurrect running programs. Storage is unchanged and stable at %APPDATA%\wmux\sessions\saved\, so it already survived the folder swap — it was just being deleted. Going forward, name + save the session you care about and it'll persist across upgrades.
Activity
fix: resolve issues #35, #39, #40, #46, #49 + bump 0.9.0
amirlehmam commentedon Jun 20, 2026
Fixed in v0.9.0 🚀 Thanks @foschmitz — and sorry for the lost session.
Root cause: on every version update, wmux ran a
handleVersionChange()that deliberately deleted all session data — including your explicitly named saved sessions — to avoid stale state freezing terminals. That was too aggressive: named sessions are layout-only snapshots (no live PTY handles), and loading one always re-spawns fresh shells (pty.createwhenpty.has(surfaceId)is false), so there's nothing stale to freeze.Now the version-change reset touches only the volatile auto-session (
session.json); your named saved sessions and the last-session pointer are preserved across updates. Added two unit tests to lock this in.One honest caveat: live processes still can't survive an app restart (the OS kills them when wmux exits). "Restoring a session" reopens the layout — workspaces, panes, tabs, and each terminal's last cwd (issue #20) — and starts fresh shells there; it does not resurrect running programs. Storage is unchanged and stable at
%APPDATA%\wmux\sessions\saved\, so it already survived the folder swap — it was just being deleted. Going forward, name + save the session you care about and it'll persist across upgrades.