Getting started

Wmux is a Windows app that keeps the terminals, dev servers and coding agents of each project together in one window, and brings them back after a restart. This page takes you from download to a working setup.

Install

Installer (recommended)

Download Wmux v0.2.0

  1. Run Wmux_<version>_x64-setup.exe. It installs for your user only, so it does not ask for administrator rights.
  2. If SmartScreen shows “Windows protected your PC”, choose More info → Run anyway. Wmux is not code-signed yet.
  3. Start Wmux from the Start menu.

Other downloads

FileUse it if
Wmux_<version>_x64_en-US.msiYou deploy software with MSI or Group Policy.
Wmux-portable-x64.zipYou want no installation. Unzip it anywhere and run Wmux.exe.

All files are on the latest release page. To check that a download is intact, compare its hash with SHA256SUMS.txt from the same release:

Get-FileHash .\Wmux_0.3.0_x64-setup.exe -Algorithm SHA256
Smart App Control. On Windows 11 PCs where Smart App Control is on, unsigned apps are blocked with no “Run anyway” option. Until Wmux is signed, it can only run there if you turn Smart App Control off (Windows Security → App & browser control).

Verify the installation

On first launch you should see:

Type a command to confirm the shell responds. If the terminal shows an error instead of a prompt, see Troubleshooting.

First steps

  1. Open a project. Press Ctrl Shift O and pick a folder. Wmux creates a workspace named after it, with a terminal already in that folder.
  2. Split the pane. Ctrl Shift D splits right and Ctrl Shift E splits down. The new terminal opens in the folder you were in.
  3. Start what you need. A dev server in one pane, tests in another, claude or codex in a third.
  4. Close Wmux and open it again. Everything is where you left it. See Session restore.
A Wmux workspace with three terminal panes.

You do not need to remember shortcuts. Ctrl Shift P opens the command palette, where you can search for any action.

Keyboard shortcuts

ActionShortcut
Command paletteCtrl Shift P
New workspaceCtrl Shift N
Open folder as workspaceCtrl Shift O
Close workspaceCtrl Shift W
Next / previous workspaceCtrl Tab / Ctrl Shift Tab
Switch to workspace 1–9Ctrl 1 … 9
New terminal tab / close tabCtrl Shift T / Q
Next / previous tabCtrl PageDown / PageUp
Split right / split downCtrl Shift D / E
Maximize or restore the paneCtrl Shift Enter
Focus the pane in a directionCtrl Alt Arrow
Swap the pane with its neighborCtrl Alt Shift Arrow
Search terminal outputCtrl Shift F
Restart terminal / clearCtrl Shift R / K
Bigger / smaller / reset fontCtrl = / - / 0
Toggle sidebarCtrl Shift B
SettingsCtrl ,

Ctrl C copies when text is selected and interrupts the running command otherwise. Ctrl V pastes. Right-click copies the selection, or pastes if nothing is selected.

Change any shortcut under Settings → Keyboard.

Workspaces and panes

A workspace is one project: a name, a color, a folder, and a layout of panes. The sidebar lists them, and Ctrl 1–9 jumps straight to one. Terminals in other workspaces keep running while you look at this one.

A pane is a rectangle in the layout. Split it to make more, drag the divider between two panes to resize them, and use the pane's buttons to split, maximize or close it. Each pane holds one or more tabs, and each tab is a terminal.

Use a workspace's menu in the sidebar, or the command palette, to rename, duplicate, pin or delete it. Workspace Settings lets you set, per workspace:

Moving terminals

Drag a tab to rearrange things. The terminal keeps running while it moves.

The pane menu can send a whole pane, with all its tabs, to another workspace. Ctrl Alt Shift Arrow swaps the focused pane with its neighbor. Press Esc to cancel a drag.

Agents

When Claude Code, Codex, Gemini CLI, OpenCode or Aider runs in a terminal, its tab shows an agent icon: pulsing while the agent is working, amber when it is waiting for you, green when it is idle. The workspace in the sidebar and the status bar show the same. Claude Code reports its own status; for the other agents, recent terminal output counts as working.

Session restore

When you open Wmux again, after closing it or after the PC restarted, each terminal comes back in its workspace, pane, tab and folder. On top of the layout, three things are restored.

Wmux after a restart, showing restored terminal text and a re-run dev server.

Terminal text

The screen and scrollback of each terminal are saved every 10 seconds and when the window closes. A restored terminal shows that text, then a session restored line, then a new prompt.

Agent sessions

While Claude Code or Codex runs in a terminal, Wmux records the agent's own session id. After a restart it runs the agent's resume command in that terminal, in the folder the agent was started in:

claude --resume <session id>
codex resume <session id>

Nothing is installed into the agents and no hooks are needed. Wmux reads what the agents already record about their running sessions.

Running commands

If a command was still running when Wmux closed, such as a dev server or a file watcher, it is started again. A command that had finished is not repeated. This needs PowerShell with shell integration turned on.

What is not restored

Commands that must not repeat. Re-running applies only to a command that was still in progress. If you sometimes leave commands running that would be harmful to start a second time, turn off Settings → Terminal → Re-run running commands.

Shell integration

Shell integration lets the shell tell Wmux which folder it is in and which command is running. It powers “open the new split in this folder”, the folder in the status bar, and re-running commands after a restart.

ShellCurrent folderRunning command
PowerShell 7, Windows PowerShellYesYes
cmdYes, unless you set your own PROMPTNo
Git Bash, WSLIf your shell emits OSC 7No

In PowerShell it wraps your existing prompt function, so your own prompt and theme are kept. Turn it off under Settings → Terminal → Shell integration.

Settings

Open settings with Ctrl ,. Changes apply immediately.

The Terminal tab of Wmux settings, including the three session restore options.
TabWhat you can change
GeneralWhether closing a workspace asks for confirmation.
AppearanceDark, light or system theme; accent color; terminal font, size and line height.
TerminalDefault shell, shell integration, the three restore options, cursor, scrollback length, copy on select, GPU rendering.
KeyboardEvery shortcut.
AdvancedWhere the database is, and the app version.

Your data

Workspaces, settings and saved terminal text live in one SQLite file on your PC:

%APPDATA%\dev.wmux.desktop\wmux.db

Nothing is sent anywhere. Saved terminal text is whatever was on screen, so it can contain anything you printed there. To keep terminal text out of the file, turn off Restore terminal text.

Set the WMUX_DATA_DIR environment variable before starting Wmux to keep the data somewhere else, for example next to a portable copy. If the database cannot be read, Wmux moves it aside, starts fresh and tells you where the old file went.

Updates

From version 0.4.0, Wmux updates itself. It looks for a new version when it starts and a few times a day; when there is one, an Update to vX button appears in the status bar. Click it and Wmux downloads the new version, installs it and restarts with your terminals restored. Nothing is installed without that click, and every update is checked against a signing key built into the app. You can also run Check for Updates from the command palette, or turn the automatic check off under Settings → General.

This works for copies installed with the setup program. MSI and portable copies, and versions older than 0.4.0, are updated by hand: download the newest installer from the releases page and run it over the existing installation. Your workspaces and settings are kept. The changelog lists what changed.

Requirements

Build from source

You need Rust (stable, MSVC toolchain), Node.js 22 or later, pnpm 9, and Visual Studio Build Tools with the “Desktop development with C++” workload.

git clone https://github.com/SahinurDEV/wmux.git
cd wmux
pnpm install
pnpm dev      # run the app with hot reload
pnpm build    # installers in target/release/bundle
pnpm test     # frontend and Rust tests

pnpm dev runs under its own app identity, so it does not touch the data of an installed Wmux.

Troubleshooting

“Windows protected your PC”

Choose More info → Run anyway. This appears because the app is not code-signed yet.

The app is blocked with no way to run it

Smart App Control is on. See the note under Install.

A terminal says “Failed to start shell”

The shell chosen for that terminal is not available. Press Enter to retry, or pick another shell from the tab's menu or under Settings → Terminal → Default shell.

An agent session did not resume

The agent must have been running for a few seconds before Wmux closed, and its command (claude or codex) must be on your PATH. A session with no messages in it has nothing to resume. Check that Resume agent sessions is on.

A command was not re-run

Re-running works in PowerShell with shell integration on, for single-line commands that were still running when Wmux closed.

Something else

Open an issue and include the Wmux version from the status bar.