cmux alternatives for the web, Linux, and teams

Updated October 14, 2026 · first published August 30, 2026 · by the AQ team

cmux (cmux.com, by Manaflow) is a free, open-source native macOS terminal built for running AI coding agents in parallel: vertical tabs that show each workspace's git branch and status, notification rings when an agent needs attention, split panes, an embedded browser, and a socket API for scripting. It is genuinely good at its job, and if you are a solo developer on a Mac you should probably just use it. People search for alternatives for three reasons, and they are the shape of the product rather than bugs: as of October 2026 cmux is macOS-only (its own FAQ says "macOS only, for now"; there is no official Linux or Windows build), it is single-player (teammates cannot watch or drive an agent working in your terminal), and the app runs on your Mac, so closing the laptop stops local agents unless you pay for cmux's hosted Cloud VM plans. The right alternative depends on which of those you are solving: tmux-based tools like ccmux and workmux reproduce the workflow on Linux, on Windows via WSL2, and in any terminal, vendor cloud agents like Claude Code on the web and Codex move execution off your machine entirely, and AQ puts the whole pattern in the browser on a VM your team shares. Honest fit notes on each below.

What cmux does well, and where it stops

First, disambiguation: two open-source projects share the name. This guide covers the Manaflow cmux, the native macOS terminal app; a separate, smaller CLI called cmux (by craigsc) wraps git worktree management for Claude Code inside tmux, and the tmux section below covers its territory.

The Manaflow cmux launched in February 2026 with a Show HN post that reached the top of Hacker News, and has grown to roughly 28,000 GitHub stars as of October 2026. It is a native Swift and AppKit app that uses libghostty (the terminal engine behind Ghostty) as a rendering library, so it inherits Ghostty's speed and reads your existing Ghostty theme. On top of that it adds what matters when six agents run at once: vertical tabs showing git branch, linked PR status, working directory, listening ports, and the latest notification per workspace; colored notification rings you can wire into agent hooks via a cmux notify CLI; split panes; session restoration after a restart; SSH workspaces for remote machines; a claude-teams command for Claude Code's teammate mode; and an embedded browser with a scriptable API agents can drive against your dev server. It installs with a DMG or Homebrew (brew install --cask cmux), requires macOS 14 or later, and the app is licensed GPL-3.0-or-later (its server components use the Business Source License 1.1). The terminal itself is free; as of October 2026 paid plans (Pro at $50 per month, Max at $200, Team at $60 per user per month, custom Enterprise) add cloud agents on hosted Cloud VMs, an iOS companion app, and centralized team billing. The earlier Founders Edition is no longer sold.

Where it stops is deliberate. It is a terminal, not an orchestrator: it will not queue tasks, manage worktrees, or review diffs, and the maintainers present that neutrality as a feature. It is a native Mac app, so Linux and Windows developers are out (the project's own FAQ says "macOS only, for now" as of October 2026, with no announced timeline for other platforms). And it has no human team layer: the claude-teams command coordinates multiple Claude Code agents, and the Team plan covers centralized billing and priority support, but a colleague cannot open one of your workspaces, see the agent's output live, or take over a session. If any of those three is your actual problem, here is the field.

cmux alternatives at a glance

Can you run cmux on Windows or Linux?

No, not officially. As of October 2026 cmux ships only as a macOS app (macOS 14 or later, Apple Silicon or Intel), installed with a DMG or Homebrew, and the project's own FAQ says "macOS only, for now". There is no Windows or Linux download, and WSL does not change that: cmux is a native GUI application, not a CLI, so the Windows Subsystem for Linux is not a path to running it.

On Linux, one unofficial port exists: cmux-linux (by bradwilson331 on GitHub) rebuilds the app in Rust on GTK4 against Manaflow's own Ghostty fork, reimplementing the workspaces, tabs, split panes, notification tracking and socket API. It is AGPL-licensed and, as of October 2026, a small single-developer project (under a hundred GitHub stars), so treat it as a community effort rather than a supported product. The sturdier Linux route is the tmux toolchain in the next section.

On Windows there is no port at all. The two practical options are running the tmux-based tools below inside WSL2, which reproduces the parallel-agent workflow in any Windows terminal, or moving to a browser-based platform like AQ, where the agents run on a cloud VM and the whole interface is a web page that works in any browser on Windows.

On Linux or Windows: tmux is the native answer

cmux is, at heart, a beautiful multiplexer for agent sessions, and the original multiplexer runs everywhere. A workable Linux equivalent is plain tmux plus git worktrees: one window per task, one worktree per window, an agent CLI in each. You lose the sidebar and the notification rings, but you gain something no laptop app can offer: run the same setup on a server and your agents survive disconnects and lid closes.

Two open-source projects automate the pattern. ccmux runs your agent CLIs (Claude Code, Codex, Cursor, and others) in tmux with a background daemon that watches session activity and a TUI showing live states, so you can jump straight to the agent that needs input. workmux goes further on worktree automation as of October 2026: one command creates a worktree and a matching tmux window with your agent started, workmux merge merges the branch and then cleans up the worktree, window and local branch, and it ships status hooks for Claude Code, Codex, OpenCode and several other CLIs (MIT-licensed, installable with Homebrew or Cargo, tmux as the main backend with experimental Zellij, WezTerm and kitty support). Both are free and run anywhere tmux does, including WSL2 on Windows. If you want cmux's rendering quality on Linux, Ghostty itself is cross-platform (it ships in the Ubuntu 26.04 LTS repositories as of April 2026) and pairs fine with tmux.

If the real problem is the laptop: move execution off your machine

A common reason people outgrow any local terminal, cmux included, is that the sessions die with the machine. One route is the vendor clouds. Claude Code on the web runs sessions in isolated VMs managed by Anthropic, in parallel, against your GitHub repository; as of August 2026 it is available on Pro, Max, Team, and Enterprise plans, and Anthropic opened a public beta of self-hosted environments (execution on your own servers) for Team and Enterprise plans on August 6, 2026. Codex takes the same shape on OpenAI's side: cloud tasks in isolated sandboxes preloaded with your repository, several queued at once, included with paid ChatGPT plans. The trade against cmux is control and choice: the vendor's agent in the vendor's sandbox, driven from a task queue rather than a live terminal you can type into. The cloud coding agents roundup compares these in depth, and background agents vs cloud agents untangles the vocabulary.

The other route keeps the terminal experience and moves it to a VM you control: agent CLIs in tmux on a cloud box, attached from anywhere. That is the pattern running Claude Code on a cloud VM walks end to end, and the foundation AQ productizes below. cmux points partway there with SSH workspaces and, on its paid plans as of October 2026, hosted Cloud VMs, but the front end remains a Mac app.

If you want an orchestrator instead of a terminal: Conductor

Some people searching for cmux alternatives actually want more automation, not a different platform: task queues, managed worktrees, diff review. On the Mac, Conductor is the established orchestrator: parallel Claude Code, Codex, and Cursor agents, each in an isolated worktree, free for local use, with cloud workspaces and an invite-only team tier on paid plans as of August 2026. It is also Mac-only, so the platform constraint does not improve. Our Conductor alternatives guide covers that branch of the decision tree.

Where AQ fits: the multiplayer, browser-based take

AQ is the multiplayer coding harness where engineering teams run AI coding agents like Claude Code and Codex together: shared live terminals, a code editor, and app previews, in your own cloud.

Against cmux's three limits, AQ's answers are direct. Platform: AQ runs in the browser on macOS, Windows, Linux, and mobile. Persistence: agents run as real CLIs (Claude Code, Codex, Cursor Agent, Kimi, Grok, or plain shells) in persistent tmux sessions on your team's VM (one you connect from your own cloud, or a dedicated always-on AQ-managed VM), streamed live to the browser, so sessions survive a closed laptop and resume from any device. Team: teammates open the same workspace and watch the same live session; typing into someone else's terminal is delegated by its owner approving a control request in one click, and workspaces are team-visible or private and shared with specific people, at the owner's choice. The parallel-agent mechanics cmux leaves to you are built in: each workspace gets an isolated git worktree (branch ai/{id}-{slug}, automatic dependency install, one-click rebase onto main), agents commit and open PRs with per-user GitHub auth, PRs are tracked per workspace, and each workspace can run a live dev-server preview with shareable links that work without an account for viewing. Like cmux, AQ never resells your own subscriptions: you log into each CLI with your own Claude or OpenAI account and that usage is never marked up.

The honest trade: cmux is a native local app and AQ is not. If you want GPU-fast rendering in a Mac window for solo work, cmux is better at being that. AQ earns its place when sessions need to outlive a laptop or be seen by more than one person. Pricing is two plans: Free is a personal sandbox for one person (AQ creates a private machine in an isolated network, nothing to install, no time limit), and Team is $50 per user per month early access (standard $200, billed monthly), covering VMs you connect from your own cloud or a dedicated AQ-managed VM, with the rate locked for your first 12 months. There is no shared multi-tenant execution tier: your agents run on your VM.

How to choose

Solo on a Mac and happy with local sessions: use cmux, it is free, open source, and excellent at its job. Same workflow on Linux or Windows: ccmux or workmux on tmux (inside WSL2 on Windows), which also sets you up to move to a server later. Sessions that must survive the laptop: a vendor cloud agent if the vendor's sandbox and agent suit you, or the cloud VM pattern if you want your own box. More orchestration on the Mac: Conductor. And if the goal is your team running many agents in one place, watching and steering the same live sessions from any OS, that is the case AQ was built for; the Free sandbox is the no-cost way to test whether the multiplayer claim holds up.