Skip to content

WinMux

tmux, outside the terminal. Split your screen into panes, put anything in them, and get the whole arrangement back tomorrow.

A terminal multiplexer splits a terminal into panes. WinMux splits a window into panes, and a pane can hold a terminal, an ordinary Windows application, or a file browser. The arrangement — the splits, the tabs, what each pane was running and which directory it was in — is written to a file and restored next time.

Panes that hold anything

Terminals run on ConPTY with a real VT engine. Ordinary applications are hosted in their own process so a frozen one cannot freeze WinMux. A file browser is built in.

Sessions that come back

Layout, tabs, programs, arguments and working directories are saved continuously and restored on launch. Restoring recreates processes; it does not restore what was inside them.

Keyboard first, not keyboard only

A tmux-style prefix by default, and every action is also a button, a command-palette entry and a CLI command — the same named action behind all four.

It looks like Windows

Mica, the system accent, light and dark following the OS, and the toolbar in the title bar with real snap layouts.

WinMux restores processes, not process state. A restored shell is a new shell in the right directory, not the one you left with its scrollback and running jobs. Nothing can restore those, and saying otherwise would be the fastest way to make the feature look broken.

Application compatibility is real but not universal. Some applications refuse to be embedded and are hosted alongside instead; elevated ones cannot be hosted at all. See Troubleshooting.