DEV Community: Crystal Studio

umux 1.6.2: ping me when you're stuck

Crystal Studio — Tue, 15 Sep 2026 19:06:38 +0000

umux is a free, open-source terminal workspace manager for Linux, Windows and macOS. One workspace per project, tabs inside it, and every tab splits into as many panels as you need. The feature the app is built around: umux reads the OSC 9;9, 99 and 777 escape sequences that AI CLIs like Claude Code emit when a long task finishes, and turns them into a desktop notification.

Landing: https://umux.pages.dev
GitHub: https://github.com/CrystalPlatforms/umux

v1.6.0 taught the app to ask which shell you use. v1.6.2 teaches it to notice when your agent stops mid-task and waits for you. The release hangs on one gap: until now the bell rang only at the finish line, and agents spend much of their time before it, parked on a permission prompt nobody announced.

The ping for waiting agents

umux tracks a status per panel: working, needs-attention, or nothing. The flip from working to needs-attention used to be a silent one. In 1.6.2 it rings the same bell a finished task does, under the same single Desktop notifications switch.

A gate keeps it to one ping per waiting session. Terminal UIs repaint on a cycle, and the flip can happen every ten seconds during a repaint. Without the gate you would get rung every ten seconds. With it you get rung once, and the next ping waits for a genuinely new wait.

Click through to the panel

A notification that tells you something happened is good. A notification that takes you there is better. The banner carries its workspace, tab and panel, and clicking it navigates straight to the panel the agent sits in. Linux hangs an Open action on the banner. macOS and Windows route a focus heuristic that stays valid for 60 seconds after the ping.

Quiet is an answer too

The end of a wait is not always announced. CLIs without completion escapes never say they are done; they stop talking. After you answer, a reply that streams and then goes quiet now drops the panel back to needs-attention after 10 seconds of silence, down from about 60.

Windows: folder lines go live

The sidebar's folder lines work on Windows now, live. Reading another process's working directory there means reading its PEB. And PowerShell never syncs its own process cwd when you cd, so umux chains a prompt hook that syncs the working directory and emits the OSC 9;9 report, without ever overwriting the prompt you see. cmd gets the same through a PROMPT override. The parser surfaces those reports with the byte stream untouched, and the sidebar folds a folder change in instantly, ahead of the 20-second snapshot. SSH panels ignore the reports: a remote path is not a local cwd.

A tooltip that answers in time

The ports tooltip on Windows used to spawn a PowerShell query per hover, about 0.6 seconds, and the answer landed after your cursor had left the row. It reads a Toolhelp32 snapshot now, about 10 ms. The answer arrives while you are still looking at it.

One more from daily use: a new tab inherits the folder of the tab you were on. SSH tabs and session restore keep their own rules.

The sidebar keeps its width

The honest list in the last post said drag-to-resize worked on macOS only. This release closes that line. The width persists across restarts on all three operating systems, saved on drag release and again 400 ms after the last move, because release events do not always arrive. A restored width clamps to the live window's limits.

Folder lines learned to merge in the same pass. With agent status on, every tab keeps its own line and its own chip. With agent status off, tabs sharing a folder share one line, drawn at the first of them. Lines without a folder never merge.

Small things

The app boots behind a splashscreen now, and the main window appears with a two-second beat so the splash is actually seen.

The numbers

The app-side diff is 26 files: about 2,600 lines added and 240 removed. The frontend suite sits at 739 passing tests, up from 700 at v1.6.1. The growth is mostly new suites: the waiting-ping gate and its decay, notification routing, folder-line merging, and the new-tab inheritance.

The honest list

Import from cmux still does not work on Windows. X11 sessions are untested; Wayland is the reference platform. Agent status took its biggest step in this release and still has edges to sand.

The installers: .deb, .AppImage and .rpm on Linux, a universal .dmg on macOS 11+, an NSIS installer on Windows 10+. MIT licensed, no accounts. The in-app updater picks 1.6.2 up on its own.

Landing: https://umux.pages.dev
GitHub: https://github.com/CrystalPlatforms/umux

umux 1.6: Any Shell in Any Tab

Crystal Studio — Thu, 10 Sep 2026 18:36:22 +0000

Landing: https://umux.pages.dev
GitHub: https://github.com/CrystalPlatforms/umux

The last four releases were repairs. v1.5.2 smoothed Windows, v1.5.3 fixed five things on macOS, v1.5.4 killed a bug every packaged build had carried since the first one. v1.6.0 is the release in this streak that only adds.

The shell picker

New tabs open in your default shell, and until now that default was whatever your operating system decided. Settings asks you properly in 1.6.0: pick from the shells detected on your machine, or type a custom command for anything the detector misses.

Detection needs no setup. A PATH scan backs the list on all three systems. On Unix it reads /etc/shells and your login-shell record, so bash, zsh and fish show up as themselves. On Windows it checks the registry, and WSL distros land in the list next to PowerShell, cmd and Git Bash.

One arrow, and only when it means something

The "+ New tab" button grows a small arrow. It opens a dropdown that spawns one tab in a different shell, leaving your default alone. Spawn a fish tab to test a config, keep working in zsh.

The arrow obeys one rule: it exists only when there is a real choice. A machine with a single installed shell shows no arrow at all, because a dropdown with one item is noise. The picker affects local tabs only; SSH sessions keep the remote machine's login shell, exactly as before.

The sidebar, on your terms

Two switches ship in Settings, both off by default.

The first hides the git branch on tab rows, for the days you want the sidebar quiet. The second lists working directories on workspace rows: one line per tab, that tab's agent-status chip next to the folder its shell sits in. Every tab gets a line and duplicates stay unmerged. The data comes from the directories umux already tracks.

Small things

Tabs go full screen, and ESC brings them back. The accent rails on workspace and tab rows now run the full row length in a straight line. The Settings dialog title is larger. All three came out of using the app daily.

The numbers

Twelve commits since v1.5.4. The diff adds about 3,800 lines and removes 200 across 41 files. Six new modules ride along: the shell detector with its test suite, the per-tab folder model with its own tests, and the Rust-side shell probe. The frontend suite sits at 698 passing tests, up from 616 at v1.5.4.

The honest list

Import from cmux still does not work on Windows. X11 sessions are untested; Wayland is the reference platform. Agent status is still the roughest feature in the app. The sidebar's drag-to-resize gesture works on macOS only so far; the cross-platform fix with a persisted width is queued for a small v1.6.1 patch. After that comes the big rock: the umux Core daemon.

The installers: .deb, .AppImage and .rpm on Linux, a universal .dmg on macOS 11+, an NSIS installer on Windows 10+. MIT licensed, no accounts, and one anonymous app-open event is the entire telemetry. The in-app updater picks 1.6.0 up on its own.

Landing: https://umux.pages.dev
GitHub: https://github.com/CrystalPlatforms/umux

Four releases, five days, one phantom that hid behind a minified name

Crystal Studio — Mon, 07 Sep 2026 12:47:01 +0000

Landing: https://umux.pages.dev
GitHub: https://github.com/CrystalPlatforms/umux

This covers four releases in five days. v1.5.1 gave workspaces colors and taught the cmux import to carry them over. v1.5.2 was the Windows smoothness pass. v1.5.3 fixed five things on macOS. And v1.5.4 killed the bug this release is named after: a terminal that worked in every dev build and died in every packaged one.

v1.5.2: what it takes to stop a terminal from stuttering

The Windows build passed every test and felt bad anyway. Output stuttered while a command streamed. Empty console windows flashed on hover. Four causes, four fixes.

PTY bytes crossed to the WebView as a JSON array of numbers, so one byte became up to four characters of JSON. They travel as base64 now, four times smaller, one decode on arrival. OS work ran on the UI thread: process lookups, working directories, listening ports, git branches, store saves. All of it is asynchronous now, and the PTY mutex is held only long enough to read a pid. The foreground-process lookup spawned tasklist.exe per check; it is one call to OpenProcess plus QueryFullProcessImageNameW now. And every shell-out passes CREATE_NO_WINDOW now: netstat, the PowerShell CIM queries, the toast notifier. The phantom console windows are gone.

The terminal also renders through xterm.js's WebGL addon since this release, with a fallback to the DOM renderer if the GPU context dies.

v1.5.3: five fixes from one macOS report

One report turned into five fixes. The WebGL addon renders a black canvas on Apple WebKit and WebKitGTK: the context creates fine and presents nothing. It loads on Chromium-based webviews only now, with the DOM renderer everywhere else. A GUI-launched app has no $SHELL, so panels ran /bin/sh and loaded none of your config; the shell resolves through getpwuid now. The bare monospace font renders Courier in WKWebView; the stack is ui-monospace/Menlo/Consolas/DejaVu. A dead working directory fell back to the app's own cwd instead of your home. And a relative "." from lsof no longer gets stored as a panel directory.

v1.5.4: works in dev, black in production

Then the report this release is named after. Third-party CLIs like Mistral Vibe and OpenCode start inside umux, and the panel goes black. Claude Code runs fine. Typing feels dead. Closing the tab is the only way out.

The first suspect was ours and wrong. The OSC parser really did eat Kitty notification queries (ESC]99;…p=?) and really did mistake ConEmu progress reports (ESC]9;4;…) for task completions. Both fixed. The phantom "4;0;" notifications from Claude Code panels stopped. But byte captures showed the TUI stream passing through the backend intact, so the loss lived between the IPC bridge and the pixels.

Instrumentation came next: an opt-in, flag-file-gated dump that logs byte counts per chunk and DOM character counts per panel. Numbers only, never terminal content. It showed something that made no sense: the bytes arrived, the DOM held the TUI's text, and the screen stayed black. That pushed the hunt toward compositing theories. All of them were wrong.

What cracked it was a harness. The real production bundle, served the way the packaged app serves it, a mocked IPC layer, and a recorded byte stream replayed into real WebKit. The black screen reproduced in minutes, and the console held the answer:

ReferenceError: i is not defined
 at requestMode

xterm.js 6.0.0 ships pre-minified. Inside its requestMode handler, a closure captures a parameter, and an enum initializes through a polyfill pattern. Vite's build step re-minifies that code a second time, the names stop existing, and the first mode query a modern TUI sends at startup throws. That query is ESC[?2026$p, the synchronized-output probe. The exception kills xterm's write worker. Nothing renders after it. Nothing you type changes what you see.

Upstream issue xtermjs/xterm.js#5800 describes this bug word for word, down to the console line. Another terminal project hit the same crash. The fix ships with umux as a patch-package patch: the enum polyfill becomes a plain object, and the flag moves into a local constant before any closure can capture it. npm install applies the patch, and a contract test locks the synchronized-output paint behavior in place.

The same release paints DEC 2026 frames the moment their block closes. xterm otherwise debounces the paint into a window the next frame's sync block can invalidate, which freezes a fast full-screen TUI to about one frame per second. And the diagnostics mode stays in the build, flag-gated, for whoever hunts the next ghost.

The numbers

Four releases. v1.5.4 lands as +779/−28 across eight files plus the xterm patch. The frontend suite sits at 616 passing tests, the Rust suite at 97, plus a WebKit harness that runs the real bundle against a recorded stream. That check would have caught this bug before any user did.

The honest list

Import from cmux still does not work on Windows. X11 sessions are untested; Wayland is the reference platform. Agent status is still the roughest feature in the app. The umux Terminal TUI, with the herdr importer, is the next big rock. Planned for v1.7.

Landing: https://umux.pages.dev
GitHub: https://github.com/CrystalPlatforms/umux

If a terminal inside umux ever went black on you: v1.5.4 is the one to install.

Every workspace in umux gets a color now, and cmux colors come with you

Crystal Studio — Sat, 05 Sep 2026 06:29:40 +0000

Landing: https://umux.pages.dev
GitHub: https://github.com/CrystalPlatforms/umux

The last post here covered v1.0.2 through v1.0.4: the cmux importer, in-app updates, and the offline CLI. Today's release is v1.5.1. Eight commits, about two thousand lines added, and one idea carrying the release: color.

The gray-objects problem

Every row in a terminal manager's sidebar is text. With six projects open, telling them apart means reading, every time, in the sidebar and in the tab bar. v1.5.1 lets each workspace carry a color instead. There are eight, chosen from the workspace's context menu.

The color shows up in small places. A square swatch sits beside the workspace name, and a colored edge runs down the left side of the app while that workspace is active. Tabs get the same treatment: a swatch in the tab bar and a colored strip along the top edge while the tab is active. Groups tint their folder icon. A pinned workspace wears its color on the pin, because the pin is the one mark that is always visible.

Your cmux colors come with you

The part I like most is what happens on import. cmux stores an accent color per workspace and per group as free-form hex: whatever you picked, sixteen million options. umux has a fixed palette of eight. The importer maps every cmux color to the nearest palette entry by squared RGB distance, and the setup arrives looking the way it looked before. Not exactly the same. Nearest.

The mapping is strict on purpose. Only a well-formed #RRGGBB string maps to a palette entry; anything else imports as no color at all. A wrong guess sits in your sidebar forever, but gray costs two clicks to fix.

One detail only shows up when you read cmux's files closely: the actions in cmux.json carry no colors. The session store is the only place colors live, so it is the only place the importer reads them from.

One import, two implementations, one suite

The color mapping exists twice, like everything in the importer: TypeScript in the in-app wizard, Rust in the umux import cmux CLI. The golden-fixture parity suite keeps both honest — the fixtures of cmux state now carry color cases, and one expected plan says exactly which palette entry each maps to. If the two implementations drift, a test goes red before either ships a wrong color. umux import cmux --dry-run still prints the plan and writes nothing; the plan carries the mapped colors, so you can read where everything landed before anything lands.

Ports you can click

The ports tooltip has always listed which local ports your dev servers are listening on. Now a click on a port opens http://localhost:PORT in your browser. The URL still lands on your clipboard too, because copy-on-click is muscle memory nobody should have to unlearn. The new dependency doing the opening is tauri-plugin-opener.

The small stuff

The inline rename pencil is gone from workspace and group rows. Renaming lives in the context menu — one place, not two.
The × next to a workspace now deletes it, behind a confirmation. It used to just close it, which read like deleting and wasn't.
Settings has a Reset umux button. Two clicks wipe every state file (workspaces, layouts, settings) and the app relaunches into its first-run state. A factory reset for when an experiment goes wrong.

About the version number

v1.5.1 follows v1.0.4 directly. The jump is bookkeeping: the roadmap's version numbers got renumbered so the roadmap and the shipped tags stay in step. The app just carried on.

The honest list

Import still does not work on Windows, same as in the first post. X11 sessions are untested; Wayland is the reference platform. Agent status is still the roughest feature in the app, and the completion notification is still the solid part.

Between the last post and this one: 8 commits, +2,127/−192 lines, roughly 950 of them new test code. The installers: .deb, .AppImage and .rpm on Linux, a universal .dmg on macOS 11+, an NSIS installer on Windows 10+. MIT licensed, no accounts, and one anonymous app-open event is the entire telemetry.

Landing: https://umux.pages.dev
GitHub: https://github.com/CrystalPlatforms/umux

If you color your workspaces in cmux and assumed a switch meant repainting everything by hand: it doesn't. Run the dry run and read the mapped palette before anything moves.

We built a free terminal manager for 3 platforms. Four days later it imports cmux setups

Crystal Studio — Tue, 01 Sep 2026 17:37:52 +0000

v1.0.2 shipped on August 27. It was the first release with native builds for all three platforms. Four days later the tree sits at v1.0.4, with 26 commits and two releases in a single day behind it. Here is what went in.

Landing: https://umux.pages.dev
GitHub: https://github.com/CrystalPlatforms/umux

The first feature after launch was a door out of cmux

cmux is the closest project to umux, and a good one: macOS only. Launching a cross-platform alternative and waiting for people to switch is the obvious move. But switching means rebuilding your workspace setup by hand, and my bet is that cost kills more migrations than missing features do. So the importer came first.

It reads cmux's state strictly read-only and builds a plan: workspaces, groups, sidebar order, working dirs, tabs. You preview the plan before anything lands. umux import cmux --dry-run prints the resolved tree and writes nothing. Name collision? Nothing gets overwritten. "api" becomes "api from cmux". Taken too? "api from cmux 2".

Two implementations exist. The in-app wizard is TypeScript, the CLI command is Rust. A parity suite keeps them honest: golden JSON fixtures of cmux state, one expected plan, and a test that goes red the moment the two drift apart.

The app updates itself, for $0

v1.0.3 added in-app updates. The app checks at startup, and one click downloads, verifies and relaunches. The update bundles carry a minisign signature, and the app verifies them before install. The installers themselves stay unsigned. Code-signing certificates cost money, and this project's whole budget is $0. Same for the update server: it is GitHub Releases. The free CDN that serves the installers also serves latest.json to every running copy.

The CLI rides in every installer

v1.0.4 put the umux CLI on PATH in every installer, Windows included. It works offline against the same store the app uses. umux list prints your workspaces as JSON, umux new, rm, rename and split edit them, and umux export writes a neutral backup format. One more: umux notify shows a desktop notification with the app closed. Your cron jobs can use it too.

curl | sh, with a test suite

The newest piece is install.sh. One line on macOS or Linux:

curl -fsSL https://raw.githubusercontent.com/CrystalPlatforms/umux/main/install.sh | sh

213 lines of POSIX sh. There is no jq dependency; the script parses the GitHub API response with sed. On macOS it mounts the universal .dmg and copies the binary out of the app bundle. On Linux it opens the .deb in place with ar and tar and extracts usr/bin/umux. Nothing lands outside the install directory (~/.local/bin by default).

The odd part: the script has its own Vitest suite. 102 lines that invoke sh install.sh --dry-run the same way a user's pipe would, kept deterministic through the script's own environment hooks so the tests never touch the network. One test guards a real gotcha: release tags are v-prefixed (v1.0.4) and asset filenames are not (umux_1.0.4_universal.dmg), so a user pinning either form must land on the same file. The real download path got verified by hand on macOS against v1.0.4. Both the .dmg mount and the .deb extraction produce a working umux --version.

Also landed

Workspaces nest into groups now: a tree in the sidebar, drag & drop, multi-select, and a collapsed-group badge that shows how its AI agents are doing. The landing page got a proper install section and a new logo. Tests: 722 across frontend and Rust, up from 449 at launch, all green on today's HEAD.

The honest list

Import does not work on Windows yet. Agent status (working, needs attention, idle) is the roughest feature in the app; the completion notification is the solid part. X11 sessions are untested; Wayland is the reference platform.

The app itself: .deb, .AppImage and .rpm on Linux, a universal .dmg on macOS 11+, an NSIS installer on Windows 10+. MIT licensed, no accounts, and one anonymous app-open event is the entire telemetry.

Landing: https://umux.pages.dev
GitHub: https://github.com/CrystalPlatforms/umux

If you run cmux on a Mac and ever wondered what your setup would look like somewhere else — the dry-run is non-destructive by design.

umux: an open-source terminal workspace manager for Linux, Windows, and macOS

Crystal Studio — Fri, 28 Aug 2026 10:51:03 +0000

TLDR

umux is a free, open-source desktop app that organizes terminal windows into named workspaces (one per project), each holding tabs that split into any number of resizable panels. It runs natively on Linux, Windows, and macOS from one codebase. It also watches the terminal data stream for the signals AI coding tools emit when a long task finishes, and fires a desktop notification — so you can step away while an agent works. Version 1.0.2, released 27 August 2026, is the first release with native Windows and macOS builds alongside Linux. It exists for developers who want the "many terminals, one place" workflow without learning tmux.

Key facts

Platforms: Linux (.deb, .AppImage, .rpm), Windows 10+ (.exe installer), macOS 11+ (universal .dmg — Apple Silicon and Intel in one file)
Current release: v1.0.2, 27 August 2026; nine tagged releases in total, from five dev previews to the 1.0 line
Development timeline: 53 commits between 27 June and 27 August 2026; 42 of them in August — the active build took under a month
Tests: 449 automated tests (115 Rust + 334 frontend), all passing at v1.0.2
Stack: Tauri v2 — a Rust backend, a React + TypeScript frontend, terminals rendered with xterm.js
Licence and cost: MIT; builds are unsigned; infrastructure cost is $0 (GitHub Actions for builds, Cloudflare Pages for the landing page)
Telemetry: exactly one anonymous app-open event, nothing else
Layout model: workspaces → tabs → unlimited split panels per tab, with minimum panel sizes and one-shortcut pane zoom

Key fact: terminal output inside umux is byte-identical whether or not its inspector is running — the inspector reads the stream and never modifies it.

What is umux?

umux is one window where all of a project's terminals live. A developer creates a workspace named after the project — "shop-frontend", "server-migration" — and opens terminal tabs inside it. Any tab's area splits into as many panels as needed, resized by dragging dividers, with a minimum size enforced so nothing collapses to nothing. A keyboard shortcut zooms one panel to fill the tab and restores the exact previous layout afterwards; the covered panels keep running underneath.

The whole arrangement survives a restart. Workspaces, tabs, panel layouts, and working directories are saved to a config file and restored when the app reopens. Each panel runs a real shell — the user's own shell on Linux and macOS, PowerShell on Windows — and renders a genuine terminal: colors, cursor movement, full-screen programs like vim and htop all work.

What problem does it solve?

A working developer's terminal count grows with every project. Today's typical setup: a dev server in one window, an API in another, an SSH session into a remote machine somewhere, plus an AI coding agent churning through a task in a fourth. The windows pile up in the taskbar and the developer loses track — most acutely when an AI agent finishes a ten-minute task and nobody notices for twenty minutes.

Quick answer: umux replaces the window pile-up with one window per project, and it tells you when the AI agent is done instead of making you babysit it.

The classic tool for this is tmux, and it is genuinely excellent — but it is a keyboard-first, text-mode world with its own prefix keys and configuration language. Plenty of good developers never learn it. umux delivers the same outcome (many terminals, one place, organized per project) through a graphical interface.

How does umux work?

umux is one app with two halves, built on Tauri v2.

The Rust backend owns everything that touches the operating system. It creates pseudoterminals (PTYs — the mechanism that makes a program believe it is talking to a real terminal), writes keystrokes into them, resizes them, and closes them cleanly. It also handles SSH connections, desktop notifications, and the config file.

The frontend (React + TypeScript) renders the workspace UI and a real terminal surface per panel using xterm.js. Keystrokes flow from the terminal surface down to the backend; output flows from the PTY back up to the screen.

Key fact: local panels and SSH panels are the same thing to the rest of the app — both are just a PTY behind one interface — so a remote machine's terminal behaves exactly like a local one.

How does umux know when an AI agent finished a task?

Terminals and the tools running inside them communicate through escape sequences — special byte patterns embedded in the normal output stream. AI CLI tools such as Claude Code, Codex, and Aider emit standard OSC escape sequences (OSC 9;9, OSC 99, OSC 777) when a long task completes.

umux feeds every byte of terminal output through a small parser that recognizes these sequences and turns them into events. An event becomes a native desktop notification, and it also drives a per-panel agent status indicator: working while the agent streams, needs-attention when it waits for the user, idle once it exits.

Three properties of this design matter:

No polling. umux never checks whether a process is still running on a timer.
No screen scraping. umux never reads the visible terminal content to guess what is happening.
No mutation. The parser passes every byte through unchanged and only extracts events, so output stays byte-identical whether or not umux inspects it. Detection relies solely on the escape sequences — nothing else.

How does umux compare to tmux, cmux, and Herdr?

Quick answer: pick tmux if you already live in a keyboard-driven terminal workflow; pick umux if you want that outcome in a GUI — with cross-platform builds the others don't all have.

	umux	tmux	cmux	Herdr
Type	desktop app (GUI)	text-mode multiplexer	native macOS app	CLI/TUI multiplexer
Platforms	Linux, Windows, macOS	Unix-like (Windows via WSL)	macOS only	terminal-based
Interface	point-and-click + shortcuts	keyboard prefix, config file	GUI sidebar	keyboard prefix (Ctrl+B)
Agent-finish notifications	yes, from OSC signals	no	yes	agent-aware
Learning curve	install and use	prefix keys, copy mode, config language	install	prefix keys

cmux and Herdr both target the same new audience — developers running AI coding agents — and both are solid tools. The gap umux fills, per its creator: cmux carries more features than he needed and ships only for macOS; Herdr is a terminal-world tool with no desktop app. umux is the middle option — a simple desktop app, three platforms, one codebase.

What are the known limitations?

Agent status is the least polished feature. By the creator's own admission it does not yet work perfectly. The completion notifications it is built on are the solid part.
Builds are unsigned. umux ships without paid signing certificates (a deliberate $0-cost policy), so macOS Gatekeeper and Windows SmartScreen show a one-time first-run warning. The README documents the two-click workaround.
SSH panels run on Linux and macOS today; Windows SSH support is planned for v2.0.
Linux is the reference platform (Ubuntu on Wayland is what gets tested). X11 sessions are untested.

Steps: how to install umux

Download from umux.pages.dev or the GitHub releases page.
Pick the format: Linux — .deb (installs into the system) or .AppImage (portable, no install); macOS — drag the .dmg app to Applications; Windows — run the .exe installer.
First run of an unsigned build: on macOS, right-click the app and choose Open (once); on Windows, SmartScreen → More info → Run anyway (once). The README documents both.
Create a workspace per project, add a tab, split it into panels. The layout, working directories, and shells come back after a restart.

FAQ

Is umux free?

Yes. It is MIT-licensed open source, the builds cost nothing to make (GitHub Actions), and nothing in the toolchain is paid for — including certificates, which is why builds are unsigned and the README documents the first-run steps.

Which operating systems does umux support?

Linux (Ubuntu/Wayland is the reference), Windows 10 and newer, and macOS 11 and newer. The macOS build is universal — one file covers Apple Silicon and Intel. Each platform gets its own native shell: PowerShell on Windows, the user's shell elsewhere.

Do I need to learn keybindings or write a config file?

No. umux is point-and-click first: workspaces are created and renamed in the UI, panels are split and resized by dragging, and a handful of shortcuts (such as pane zoom) speed up daily use. There is no configuration language to learn.

How does umux detect that an AI coding agent finished?

It reads the standard OSC escape sequences (OSC 9;9, OSC 99, OSC 777) that AI CLI tools emit on task completion, straight from the terminal byte stream. No process polling, no screen reading. The same signals drive a per-panel agent status indicator.

Does umux change my terminal output?

No. The inspector sits beside the stream, not in front of it: every byte passes through unchanged, and detection relies solely on the escape sequences. Output is byte-identical whether or not umux is running.

Is umux a tmux replacement?

Not for people already productive in tmux — it does not aim at them. It is an alternative for the larger group that never adopted tmux's keyboard-first world and wants the same organization through a GUI. There is no config file and no modal editing model to learn.

What data does umux collect?

One anonymous app-open event, used to estimate active usage. Nothing else — no terminal content, no file names, no telemetry of any other kind. It can be turned off.

Can umux connect to remote machines?

Yes. An SSH panel opens a shell on a remote machine using the local SSH agent and keys, and behaves identically to a local panel. SSH on Windows is planned for v2.0.

How long did it take to build?

Under a month of active work. The commit record spans 27 June to 27 August 2026 (53 commits), with 42 of them landing in August.

Last updated

2026-08-28