Hey @wanwanzaizai — thanks for the report. You found a real bug; fix is shipped in v0.7.21.

Root cause

The 30s rolling auto-save was writing %APPDATA%\wmux\sessions\session.json correctly — your workspaces were in that file. But on launch the app only used the file to restore the window's size/position. The renderer's restore code only loaded named sessions (the ones you'd save via the "Save Session" UI). With no manual save, every restart created a fresh "Session 1" with new UUIDs, so it looked like your data was wiped — it was actually still on disk, just never read.

What 0.7.21 does

Workspaces / splits / tabs / shells now restore from the auto-saved file on launch (no need to use "Save Session"). The previously-active workspace stays focused.
Theme, font, cursor style, scrollback, color schemes, notification prefs, browser prefs, sidebar prefs, custom keyboard shortcuts all persist to localStorage immediately when you change them, matching the pattern that was already in place for "Default shell" (issue Can't change the default shell. #12).

So now: change a theme, set up a layout, close wmux, reopen — it all comes back.

One caveat

Terminal scrollback content (the actual command output text) is not preserved across restarts. PTYs (shell processes) are killed on quit and respawned on launch with new processes, so they start empty. Preserving scrollback would mean serializing several MB per pane on every save and is out of scope here.

Grab the zip from the release page, right-click → Properties → Unblock before extracting (or run Get-ChildItem -Recurse | Unblock-File in PowerShell after extracting) to clear Windows Mark-of-the-Web. Let me know if anything still feels off.

can save data? #15

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions