Compare · cmux 0.65 vs tmux 3.8
cmux vs tmux: comparison for developers and AI agents
cmux is a macOS terminal app, built on Ghostty's rendering library, for running several AI coding agents side by side: vertical tabs that show each agent's branch and ports, rings that light up when an agent needs you, and a browser pane. tmux is a terminal multiplexer that runs anywhere, including on servers, and keeps programs alive when you disconnect. They are not rivals so much as layers: cmux on your Mac, tmux on the machines your agents run on.
On this page
Quick verdict
Quick answer
Should I use cmux or tmux?
- Use cmux if you are on a Mac, run several agents (Claude Code, Codex, Cursor CLI, OpenCode, Gemini CLI…) locally, and want to see at a glance which one is waiting for you.
- Use tmux if work has to keep running when your laptop sleeps or SSH drops, if you are on Linux, Windows (WSL) or a server, or if you script your workspace.
- Use both for remote agents: cmux as the window on your Mac, tmux on the server holding the sessions. cmux's own docs point you to tmux for this (
cmux ssh-tmux).
cmux facts on this page come from the cmux README, cmux.com and its release list, as of October 29, 2026 (latest release v0.65.2.2, October 27, 2026). cmux is macOS-only, so we have not run it ourselves. tmux facts were checked on tmux 3.8.
cmux vs tmux comparison matrix
| Dimension | tmux 3.8 | cmux 0.65 |
|---|---|---|
| What it is | Terminal multiplexer (server + client) that runs inside any terminal | Native macOS terminal app (Swift, AppKit) using libghostty for rendering |
| Platforms | Linux, macOS, BSD; Windows through WSL2 | macOS only; other platforms on a waitlist; iOS companion in beta |
| Runs on a headless server | Yes | No; cmux ssh user@host opens a remote workspace from your Mac |
| Programs survive a dropped connection or closed window | Yes, that is its job | Restores windows, panes, directories, scrollback and supported agent sessions on relaunch; live processes only with tmux underneath (cmux local-tmux, cmux ssh-tmux) |
| "Agent needs input" alerts | Bell flag in the status line, hooks you configure | Notification rings, a notification panel and macOS alerts; reads OSC 9, 99 and 777; cmux notify for hooks |
| Per-workspace metadata | What you put in the status line | Sidebar with git branch, PR status, directory, listening ports |
| Browser | No | Scriptable browser pane (navigate, read the DOM, click, type, run JavaScript) |
| Automation | 92 commands, send-keys, capture-pane, formats, hooks, control mode | CLI and Unix socket: create workspaces, split, send input, read the screen |
| Claude Code agent teams | Each teammate in a tmux pane (teammateMode tmux) | cmux claude-teams, teammates as native splits |
| Keyboard | Prefix key, fully rebindable | macOS shortcuts; terminal keys from your Ghostty config, cmux keys in Settings |
| Config | ~/.tmux.conf | ~/.config/ghostty/config (fonts, themes, colors) and ~/.config/cmux/cmux.json |
| License, price | ISC, free | GPL-3.0-or-later, free; optional paid Founder's Edition (server parts under BSL 1.1) |
| Install | brew install tmux, any package manager | brew install --cask cmux or the DMG (updates itself) |
| GitHub stars (Oct 28, 2026) | 50.0k | 28.6k |
| Homebrew installs, last 365 days | 620,304 | 60,340 (cask) |
Homebrew counts from formulae.brew.sh (formula tmux, cask cmux), read October 29, 2026.
How they fit together
tmux is a server that owns your shells, and a client that draws them in whatever terminal you are using. Close the terminal or lose the network and only the client goes away; the server and everything in it keep running until you tmux attach again. See tmux sessions.
cmux is the terminal itself: a Mac app with tabs, splits, a sidebar and a browser. It is not a fork of Ghostty; it uses libghostty as a library and reads your existing Ghostty config for fonts, themes and colors. Because it is an app on your Mac, the shells inside it end when the app quits, unless tmux holds them. cmux's README says it plainly: "cmux does not checkpoint arbitrary live process state", and for live detach and reattach it offers cmux local-tmux (which keeps sessions through quits, crashes and updates, but not through logout or restart) and cmux ssh-tmux or cmux mosh-tmux when work must continue while the Mac is offline.
Use cases: which tool fits which job
Several agents on your Mac
Four agents on four branches, and you want to know which one is stuck on a question. cmux was built for this: each workspace shows its branch, PR and ports in the sidebar, and the pane rings when the agent asks for input. tmux can do a lighter version: windows flag a bell (!) in the status line, and a Claude Code hook can write the agent's state into it (config).
Better fit: cmux.
Agents and builds on a server
A long migration, a test suite or an agent that should keep working while you are on a train. Start it in tmux on the server (tmux new -A -s agents), detach, and reattach from any terminal later. cmux cannot keep a remote process alive by itself; its docs send you to tmux for this.
Better fit: tmux (viewed from cmux if you like).
Linux or Windows desktop
cmux is macOS only. tmux runs in any Linux terminal, including Ghostty on Linux, and on Windows inside WSL2 (setup).
Better fit: tmux.
Scripting a workspace
Both can be driven from scripts. tmux has the bigger surface (every key binding is a command, plus formats, hooks and control mode) and works the same over SSH; cmux's socket API adds browser control.
Better fit: tmux for terminals, cmux if you need the browser.
tmux and cmux together: tmux inside cmux
Nothing special is needed: tmux runs in a cmux pane like in any other terminal.
ssh devbox
tmux new -A -s agentstmux new -A -s agents attaches to the session if it exists and creates it if not, so the same line works every time. Close the Mac, open it tomorrow, run it again, and the agents are where you left them.
- Prefix collisions: cmux uses macOS Cmd shortcuts; tmux uses Ctrl+b, so they do not fight.
- Notifications from inside tmux: cmux listens for OSC 9/99/777 notifications. Programs inside tmux can only send those through with
set -g allow-passthrough all(oronfor the visible pane only); the terminal bell always gets through. Details for Claude Code are in Claude Code + tmux. - Agent teams: to see Claude Code teammates as panes on the server, run the lead inside tmux with
teammateModeautoortmux(how). Locally,cmux claude-teamsdoes the same with cmux splits. - Colors and terminfo: tmux inside a Ghostty-based terminal needs the right
TERMon the server; the Ghostty + tmux guide covers the "missing or unsuitable terminal" error and true color.
Configuration side by side
tmux reads ~/.tmux.conf. A good base for agent work (checked on tmux 3.8):
# Long agent transcripts
set -g history-limit 50000
# Let agents' desktop notifications reach the terminal,
# also from panes you are not looking at
set -g allow-passthrough all
# Splits that open in the current directory
bind | split-window -h -c "#{pane_current_path}"
bind - split-window -v -c "#{pane_current_path}"Mouse support is already on by default in 3.8. Every option is on the config page.
cmux takes fonts, themes and colors from your Ghostty config, and its own settings (sidebar, tab bar, splits, behavior) from ~/.config/cmux/cmux.json and the Settings window, where cmux shortcuts are also changed.
font-family = JetBrains Mono
font-size = 13
theme = light:Catppuccin Latte,dark:Catppuccin MochaWe do not reproduce cmux.json keys here because they change between releases; see the cmux docs.
Decision checklist
Choose tmux if…
- work must survive a closed laptop, a dropped SSH connection or a terminal crash;
- you work on Linux, BSD, WSL or remote servers;
- you want one setup in every terminal you use;
- you script layouts and agents with shell commands.
Choose cmux if…
- you are on macOS and run several agents locally;
- you want to see which agent needs you without checking each pane;
- you want branch, PR and port info per workspace without configuring a status line;
- you want a browser pane your agents can drive.
Want a multiplexer that is aware of agents but runs in any terminal? herdr and tuios are newer terminal-based options covered on the alternatives page.
FAQ: cmux vs tmux
What are the primary differences between cmux and tmux?
cmux is a macOS terminal application (built on libghostty) with features for AI coding agents: a sidebar with git and port info, notification rings, a scriptable browser and a socket API. tmux is a terminal multiplexer that runs inside any terminal on Linux, macOS, BSD or WSL, including on servers, and keeps sessions alive when you disconnect. cmux replaces your terminal app; tmux runs inside one.
Is cmux a replacement for tmux?
Only for local work on a Mac where you do not need programs to outlive the app. For persistence, cmux itself uses tmux (cmux local-tmux, cmux ssh-tmux).
Can I run tmux inside cmux?
Yes. Open a cmux pane, SSH to your server and run tmux new -A -s work. cmux shortcuts use Cmd and tmux uses Ctrl+b, so the keys do not clash.
Does cmux keep my sessions after I quit or restart?
It restores windows, workspaces, panes, working directories, scrollback, browser history and supported agent sessions (Claude Code, Codex, OpenCode) when you relaunch, even after a restart. Other running programs are not kept; for that, cmux relies on tmux.
Is cmux available on Linux or Windows?
Not as of October 2026. cmux.com lists the Mac app and a waitlist for other platforms. On Linux or Windows, use tmux (on Windows through WSL2).
Is cmux free?
Yes. The app is open source under GPL-3.0-or-later. A paid Founder's Edition is optional and, per cmux.com, includes early access to cmux AI, the iOS app and cloud VMs.
How does cmux compare with Zellij?
Zellij is a terminal multiplexer like tmux, cross-platform and terminal-based; cmux is a Mac terminal app. cmux supports Zellij the same way it supports tmux (cmux local-zellij). See Zellij vs tmux.
Keep learning
Something wrong or out of date on this page? Email hello@tmux.app and we will fix it.