gmux

Running coding agents in parallel is now a normal workflow: four or five terminals, each with an agent working, each occasionally needing a human. On macOS there are tools built for exactly this. On Windows there is no native tmux, and every alternative either drops the multiplexing, drops the notifications, or wraps a browser engine to draw text.

The failure mode is not aesthetic, it is attentional. An agent finishes, or asks for permission, and nothing tells you — so you poll windows, and the machine sits idle between the moment it needed you and the moment you noticed. Closing the window kills the sessions on top of that.

gmux builds the tmux model in-app: a per-user daemon owns the ConPTYs so sessions survive closing the GUI, with sessions, windows, panes, splits and real detach/reattach on top. The wedge is notifications — any tool that emits an OSC 9, 777 or 99 escape lights its pane with a persistent attention ring, badges the taskbar and fires a real Windows toast, suppressed when you are already looking at that pane and cleared when you focus it. No SDK, no integration: it works with anything that speaks the standard escape. The grid renders through wgpu rather than a browser engine, and a named-pipe API with a tmux-style CLI lets orchestrators drive it from outside.

Every roadmap milestone from the terminal core through detach and restore shipped, plus sixteen rounds of interface work: scrollback search with match highlighting, OSC 8 hyperlinks with hover tooltips, IME input, mouse reporting, per-pane scrollback, a command palette, prompt-jump navigation, OSC 52 clipboard and busy-pane close protection. MIT-licensed, x64 and ARM64, portable — no installer.