WinMux

Ctrl+Shift+P % Free and open source, for Windows 10 and 11

tmux, outside the terminal.

WinMux splits one window into panes and tabs, and a pane can hold anything: a shell, a file browser, or an ordinary Windows application in its own process. Close it tonight, and tomorrow the same layout comes back, every program in the folder it was in.

build · cmd
C:\src\winmux> dotnet build -c Release
  WinMux.Core      → bin\Release\net10.0
  WinMux.Shell     → bin\x64\Release
Build succeeded. 0 warnings.
C:\src\winmux> 
files · C:\src\winmux
  • docs
  • WinMux.Core
  • WinMux.Shell
  • README.md
  • session.toml
notes.txt · Editor
FileEditView

Release checklist

– tag v0.9.0

– checksums.txt

%APPDATA%\WinMux\session.tomlsaved
version = 1

[[windows.nodes]]
id        = 'n0'
kind      = 'split'
direction = 'columns'
children  = ['n1', 'n2']
ratios    = [0.5, 0.5]

[[windows.panes]]
kind    = 'terminal'
title   = 'build'
program = 'C:\WINDOWS\system32\cmd.exe'
cwd     = 'C:\src\winmux'
Click a pane to focus it, then split it, give it tabs, or close it. The session file beside it is the one WinMux keeps on disk, rewritten a moment after every change.

An interactive illustration drawn in your browser, not a screenshot: those are just below. The toolbar buttons are the real ones; so is the file format.

screenshots

And the real thing

WinMux 0.8.3, the released build, on Windows 11: a tab group of shells, a file browser, and an application in a pane of its own. These are captures, not mock-ups.

WinMux with three panes: a cmd tab showing git history beside a pwsh tab, a file browser on the WinMux.Shell folder, and a web browser window embedded in the third pane showing the WinMux documentation.
Splits, tabs and three kinds of pane in one window, following the Windows light or dark setting. The application pane is a browser in app mode with no entry in the compatibility list yet, and the status bar says so.
WinMux with a tab group whose tabs run down the left edge, beside a second tab group across the top whose active tab is itself split into a file browser and a PowerShell pane.
Tab groups nest anywhere. Left, a group with its tabs down the side; right, a group across the top whose second tab is itself a split.

why

Windows has four half-solutions and no whole one

Terminal multiplexers only hold terminals. Tiling window managers rearrange your whole desktop. Tab tools group windows but forget them. Layout restorers reopen apps but give you no panes. WinMux is the intersection, in one window with one keymap.

Kind of toolPanes and tabsA process per paneNon-terminal appsLayout comes back
Terminal multiplexersWindows Terminal, WezTerm, ZellijYesYesNo, terminals onlyPartly
Tiling window managersGlazeWM, komorebiThe whole desktopYesAs loose windowsWeak
Window tabbersGroupy, TidyTabsTabs onlyYesYesNo
Layout restorersPowerToys WorkspacesNoYesYesYes
WinMuxNested, on any edgeYes, isolatedEmbedded or attachedContinuously saved

stability

A frozen app freezes its own pane, not WinMux

Putting another program's window inside yours is easy. Surviving that program when it hangs is not: one ordinary window call against a stuck application blocks the caller for as long as the application is stuck.

So WinMux never touches a hosted application's window itself. Every application pane gets its own small WinMux.PaneHost process, which holds the window and does the risky calls. When the application hangs, its host waits; the shell keeps drawing, keeps taking keys, and can still detach or close the pane.

Terminals are separate processes too, through ConPTY. Close a pane and only that pane's process tree goes.

Measured before a line of product code was written

Shell blocked while a hosted app hangs for 6 s

Window held in the shell's own process5,965 ms
Window held by a separate pane hoststayed responsive

Taking focus while a linked app is wedged

Input queues kept apart201 ms
Input queues attached4,386 ms

From spikes 3 and 5, written up in ADR 0001 and ADR 0017, including what failed on the way.

Finding each pane's folder, three ways, best answer wins

  1. The shell says so. PowerShell, cmd and bash report their folder with an escape sequence after every prompt. WinMux offers to install the one-line snippet for you.
  2. WinMux asks the process. It reads the working directory of the deepest program running in the pane, which covers a nested shell that reports nothing.
  3. The folder it started in. One unknown pane never stops the session from saving.
34 of 40scenarios recovered the right folder across pwsh, Windows PowerShell, cmd and WSL bash, with each layer recorded and timestamped.

prefix w

Sessions come back the way you left them

The layout is saved continuously, a moment after every change, and each time a pane changes folder. A crash does not cost you the session. On the next start WinMux rebuilds the tree, the tabs, each pane's program, arguments and folder.

The session is a TOML file meant for people: the tree is flattened into a list, panes are short tables, and paths keep their backslashes. A file that will not load is quarantined and reported, never silently replaced with an empty session.

What it does not do: bring back what was inside a process. A restored shell is a new shell in the right folder, without its scrollback or running jobs. Nothing can restore those, so WinMux does not pretend to.

prefix e

Four kinds of pane, one contract

Every kind is a provider behind the same public interface, so the layout, the session file and the keymap never need to know what is inside a pane. A fifth kind can be loaded from a folder beside the app.

Terminal
cmd, PowerShell, pwsh, WSL or ssh on ConPTY, drawn by a VT engine that parses 3 to 10 times faster than ConPTY delivers. Scrollback, selection, mouse reporting and copy that never steals Ctrl+C.
File browser
Built in, with details view, drag and drop between panes, a terminal at the selected folder, and the same keys on a local drive, a network share or a server.
Application
Any program from the Start Menu, or a window that is already open, adopted into a pane. Embedded when it allows it, attached alongside when it does not.
Empty
Make the pane first and decide later. An empty pane offers your profiles, every installed application and the open windows it could take in.
Profiles
A named thing you can put in a pane: a shell or an application, with its arguments and folder. Add one from the installed-app list instead of typing a path; it appears in every menu at once.
SFTP and FTP
Browse a server in a file pane and copy between it and your disk. Shares need nothing: Windows mounts them, and WinMux walks the path.
Tab groups anywhere
A tab group can sit inside a split or inside another group, with its strip on the top, bottom, left or right edge. Pin, rename and resize vertical strips.
Notifications
A program in a hidden pane that asks for you, with a bell or an OSC 9, 777 or 99 message, becomes a Windows notification.

prefix A

Honest about which apps fit

WinMux hosts an application in one of two ways. Embed takes its window into the pane, so it moves, clips and resizes with the layout. Attach leaves the window where Windows wants it and keeps it lined up with the pane, the way a tiling window manager does.

A shipped, editable compatibility list picks the way per application. When an app refuses to be embedded, WinMux keeps the same window alive, says why in plain words, and attaches it instead. You can switch any pane live, and the choice is remembered.

When WinMux closes it hands every window back exactly as it found it: parent, styles and position.

What was measured

ApplicationHosted as
Ordinary Win32 appsEmbed, restored byte-exactly on detach
Chromium-based appsEmbed
Store and packaged appsAttach; Windows refuses embedding
Apps running as administratorRefused and explained. WinMux never runs elevated to get around it.
Monitors at different scalesSupported in code, not yet verified on real hardware

Details in ADR 0003 and Troubleshooting.

prefix :

Keyboard first, never keyboard only

The default keymap is tmux-style, behind Ctrl+Shift+P so Ctrl+B stays with your terminal programs. Every action is also a toolbar button, a command-palette entry and a wmux command, and all four call the same named action.

Bindings written as a character match the character your keyboard produces, so % and : still work on a Japanese keyboard, where they sit on different keys. Replace the whole map with one JSON file, or turn the prefix off.

It looks like Windows 11 because it reads Windows: Mica, your accent colour, light and dark, the toolbar in the title bar and real snap layouts.

# Prefix, then a key
%  split right       "  split down
c  new tab           v  tab group, tabs down the side
e  empty pane        o  adopt an open window
,  rename            x  close
w  save              :  command palette

# The same actions from any script
wmux split -h
wmux focus left
wmux new-tab
wmux validate session.toml

Never elevated

WinMux installs for your account only, needs no administrator rights, and never asks for them as a workaround. It changes no PATH; typing winmux in Explorer's address bar works through a per-user registration.

Updates itself, carefully

Help → About checks GitHub for a newer release and refuses to install anything whose SHA-256 does not match the published checksums.txt. Stable releases only, unless you ask for prereleases.

Nothing phones home

No account, no telemetry. The update check is the only request WinMux makes by itself, and one setting turns it off. Servers you browse are the ones you connect to.

Get WinMux

WinMux is before 1.0: terminals, sessions, application panes and the file browser are in daily use, and the interface is still being finished. Compatibility with your applications is a measured list, not a promise. Tell us what does not fit.

Newest release

Downloads are on the GitHub releases page.

Needs the .NET 10 Desktop Runtime; setup checks for it and offers the download. The installer is per user, into %LOCALAPPDATA%\Programs\WinMux, and is not code-signed yet, so SmartScreen warns on first start. Unzip the portable copy anywhere you can write to, not under Program Files. Uninstalling keeps your sessions and settings.

Build from source

Needs the .NET 10 SDK.

git clone https://github.com/rennerdo30/winmux
cd winmux
.\run.cmd            # build and launch, isolated profile
.\publish.cmd        # the same zip a release carries

Getting started All releases