Terminal + Agents

Solo vs cmux

Open source agent terminal vs local process dashboard

Official product sites

Quick Summary

cmux is a GPL-3.0-or-later terminal and workspace tool from Manaflow. Its native macOS app uses libghostty and includes vertical tabs, split panes, an embedded scriptable browser, agent-attention notifications, SSH/Mosh workspaces, session restore, project-local commands and layouts, a Task Manager, and a CLI/socket API. A separate cmux TUI runs on macOS, Linux, and Windows.

Solo is a desktop workspace for local agents, project commands, queues, and shell sessions, with automatic self-exit and file-watch restart for commands, notifications, resource visibility, and shared configuration through solo.yml.

Choose cmux for terminal-centric local or remote work. Choose Solo for a dedicated project-process dashboard.

Who it is for

Who should choose each option in Solo vs cmux?

Choose cmux when terminal panes and agent sessions should stay together. Choose Solo when local agents and project commands should live in a separate process dashboard.

Choose Solo if the whole local project needs structure

Solo fits best when agents, services, shell sessions, queues, and shared startup commands need one dashboard and one workflow layer.

Choose cmux if the terminal itself should stay central

cmux fits best when you want tabs, panes, browser context, notifications, and fast switching between many terminal-native agent sessions.

Feature comparison

Primary purpose
Solo
Local process dashboard for agents and project commands
cmux
Terminal built for running multiple coding agents
Terminal emulator
Solo
Yes — built-in terminals and managed PTYs
cmux
Yes — native Swift/AppKit with libghostty GPU-accelerated rendering
Vertical tabs / workspaces
Solo
Yes — sidebar with process status
cmux
Yes — sidebar showing git branch, directory, ports, and notification status
Split panes
Solo
cmux
Yes — horizontal and vertical splits with directional keyboard navigation
Embedded browser
Solo
cmux
Yes — scriptable web view with API for clicks, form filling, JS eval, and screenshots
Agent notifications
Solo
Yes — native desktop notifications, in-app toasts, OSC escape sequences
cmux
Yes — blue rings around panes, unread badges in sidebar, desktop alerts when unfocused
Automation API
Solo
MCP, local HTTP API, and Solo CLI
cmux
Unix socket API + CLI tool with workspace, split, input, notification, and browser commands
Use any terminal agent
Solo
Yes — supported agents get first-party status and session features; other CLIs run as generic processes
cmux
Yes — any terminal agent (Claude Code, Codex, Gemini CLI, Amp, Goose, Aider, etc.)
Local process dashboard
Solo
Sidebar with CPU/memory stats per process
cmux
Task Manager with CPU/memory across terminals, agents, and browser webviews
Auto-restart on crash
Solo
Automatic self-exit restart for commands, with rate limiting
cmux
Manual stop/restart in Task Manager; no automatic crash policy documented
File-watch restarts
Solo
Solo yes
cmux
Shared project command config
Solo
solo.yml — version-controlled, team-shareable
cmux
.cmux/cmux.json for actions, commands, layouts, directories, and startup commands
Session restore
Solo
Processes persist while app is running
cmux
Restores layout, directories, best-effort scrollback, browser history, and supported agent sessions
Ghostty config compatibility
Solo
cmux
Yes — reads existing Ghostty config for themes, fonts, and colors
Agent hooks
Solo
First-party agent integrations and MCP tools
cmux
Install supported hooks with cmux hooks setup
Remote workspaces
Solo
cmux
SSH and Mosh workspaces; remote tmux attachment
Open source
Solo
cmux
Yes — GPL-3.0-or-later
Price
Solo
Free (4 projects, 20 processes); Pro plan
cmux
Core app free; optional Founders Edition
Platform
Solo
macOS and Windows
cmux
Native app on macOS 14+; TUI on macOS, Linux, and Windows

What each tool is

Solo

Solo is a native desktop app that gives you one dashboard for all the commands a project needs running locally. It is a process management layer, not a terminal replacement.

  • Manages dev servers, build watchers, queues, workers, and supported CLI agents
  • Starts and stops every process; commands can restart automatically after self-exit or matching file changes
  • Sends desktop notifications when something needs attention
  • Shares configuration through a solo.yml file your team can commit to version control
cmux

cmux is a terminal and workspace tool from Manaflow.

  • Native macOS app using libghostty
  • Cross-platform TUI
  • Vertical tabs, splits, embedded browser, and notifications
  • SSH/Mosh workspaces and remote tmux attachment
  • Project commands, session restore, Task Manager, and CLI/socket automation
  • GPL-3.0-or-later

Terminal vs process management

Solo

Solo includes interactive terminals and managed PTYs, but it is not trying to replace a dedicated terminal app. You can work inside Solo or keep using cmux, Ghostty, iTerm2, or another terminal alongside it.

  • Define commands in solo.yml or the UI
  • Solo runs them in managed PTYs and monitors their state
  • Command processes can restart after self-exit or watched-file changes
  • Interact with agents, commands, and shell sessions through Solo's dashboard
cmux

cmux keeps the workflow terminal-centric.

  • Workspace tabs show git branch and notification status
  • Split panes and an embedded browser keep related work together
  • .cmux/cmux.json defines reusable project commands and layouts
  • Task Manager shows CPU and memory and supports manual stop/restart
  • No documented Solo-style automatic crash/file-watch restart policy

Notification approaches

Solo

Solo's notification system is oriented around process and terminal attention.

  • Native notifications for process crashes, restart exhaustion, and supported terminal alerts
  • In-app toasts when viewing a different process
  • OSC 9, OSC 777, and OSC 99 sequences
  • Notifications are suppressed when you are already viewing the relevant process
cmux

cmux's notification system is oriented around terminal and agent attention.

  • Notification rings and unread badges
  • Notification panel and jump-to-latest action
  • Native desktop alerts when the app is not focused
  • Supported agent hooks installed through cmux hooks setup

Using them together

Solo

cmux and Solo can coexist. They address different parts of the workflow.

  • Use cmux as your terminal for interactive agent work — prompting agents, reviewing output, using the embedded browser for context
  • Use Solo to manage background infrastructure with command restart policies, shared configuration, and attention notifications
cmux

Both tools can run alongside each other.

  • If you already use cmux as your terminal, Solo adds process management for the non-agent commands in your project
  • If you already use Solo, cmux adds a richer terminal for the interactive agent sessions that Solo's built-in terminals handle more simply
Pricing

Pricing and scope

cmux is free and open source. Solo has a free tier plus a paid layer. The real comparison is whether you want terminal-centric multitasking or a separate local environment with more structure.

Solo pricing lens

Solo has a free tier for up to 4 projects and 20 processes, with Pro above that.

cmux pricing lens

cmux is free and open source.

Decision shortcut

If the terminal is the product you want to optimize, cmux is the cleaner fit. If the project environment around those terminals needs supervision, Solo earns the separate app.

Migration

What switching looks like

Moving between cmux and Solo changes where you organize local work.

  • Keep your CLI tools either way. Both can work with the same agents and shells.
  • Use Solo if you want shared startup config, app-level status, auto-restart, and a project dashboard instead of more terminal panes.
  • Keep cmux if pane-based multitasking, browser context, and terminal-native navigation are the real reasons you use it.

Common questions

Is Solo a full cmux replacement?

Not if you rely on cmux specifically for pane-heavy multitasking, browser context, and terminal-native navigation. Solo is narrower and more opinionated around project-level control.

Can Solo and cmux work together?

Yes. A pragmatic setup is to keep cmux for terminal-centric agent sessions and use Solo as the project-level layer for agents and long-lived commands.
The Verdict

cmux is a terminal and workspace tool with local and remote workspaces, agent notifications, project commands, resource views, session restore, and automation. Solo is a project-process workspace with first-party agent status, automatic command restart, notifications, resource visibility, and shared startup configuration. Choose cmux for terminal-centric multitasking, Solo for project-process supervision, or use both.

Solo preview

See what Solo actually is

Solo is a lightweight desktop terminal workspace for local agents, project commands, interactive terminals, and long-running services. It sits beside your editor, keeps your stack visible, and gives Claude Code, Codex, and the rest of your tools one shared local control surface.

Built by

Built by Aaron Francis

Solo is built by Aaron Francis, creator of faster.dev and Database School, and VP of Marketing at Laravel. He built Solo after running Claude Code alongside his own dev stack and getting tired of juggling nine terminal tabs just to keep local agents, services, and project commands visible.

He is also a dad to two sets of twins, which tends to create a strong preference for software that reduces chaos instead of adding more of it. That is why Solo keeps showing up in these comparisons as the local workspace around your tools, not another editor or orchestrator trying to absorb the whole workflow.

Illustration of Aaron Francis holding two infant car seats

Four projects, free forever.

The Free plan includes every feature, so you only need Pro after you outgrow four projects.

FreeFull-featured, with no trial or expiration.$0forever
check
Up to 4 projects
check
Up to 20 processes total
check
All features included
check
MCP integration for AI agents
check
Native notifications
check
All future updates
Get started free 
ProUnlimited projects and processes.$99/year
check
Everything in Free
check
Unlimited projects
check
Unlimited processes
check
Priority email support
check
Activate on 3 devices
check
All future updates
Get pro licenseCancel anytime with a 30-day money-back guarantee.

Team seats

Centralized billing, simple claim-link distribution

Buy seats under one Stripe subscription, then share a claim link in Slack or email. Each claimant signs in or registers and receives a normal Solo Pro license. Optional auto-grow adds prorated seats automatically when the pool is full, so your team never hits a license wall.

Buy team seats

Seats 1–3

$99/seat/yr

Seats 4–10

$89/seat/yr

Seats 11–50

$79/seat/yr

Seats 51+

$69/seat/yr

Brackets apply per seat — a 10-seat team pays $99 each for seats 1–3 and $89 each for seats 4–10.

Give every coding agent the same room to work in.

Download Solo download

Free for four projects on macOS and Windows.

Start with a terminal and add the programmable meta-harness when you need to coordinate agents with your local development stack.

“I can't live without it.”

Jesse Hanley · @jessethanley