Compare
TermFlow vs cmux
cmux pioneered the terminal built for AI agents — on macOS. TermFlow brings the same idea to Windows, macOS, and Linux, with a first-party HTTP API and MCP server instead of a CLI plus community add-ons.
Two philosophies.
cmux
The agent terminal, on macOS.
A fast, native macOS terminal built on Ghostty's engine and made for AI coding agents — split panes an agent can drive, a built-in browser it can navigate, and a live multi-agent status board. Mature and well-loved. If you work entirely on a Mac, it's excellent.
TermFlow
The agent terminal, everywhere.
The same 'a terminal agents drive' idea, but cross-platform and contract-first: a documented HTTP API and a built-in MCP server any agent can call — not a CLI plus a community MCP bridge — identically on Windows, macOS, and Linux.
Feature by feature.
| Capability | TermFlow | cmux |
|---|---|---|
| Platforms | Windows · macOS · Linux | macOS only |
| Built for AI agents | ✓ | ✓ |
| Split panes an agent controls | ✓ | ✓ |
| First-party HTTP API | ✓ | — |
| Built-in MCP server | First-party | Community bridge |
| Agent control surface | HTTP API + MCP | CLI + socket |
| Native GPU engine | Fast | Ghostty-native ★ |
| Built-in agent-drivable browser | — | Yes ★ |
| Reboot-safe session restore | ✓ | — |
| License | Free · Apache-2.0 | Free · GPL-3.0 |
Where cmux wins
cmux got here first, and it's a genuinely great product — mature, fast, and native on macOS, with a built-in browser an agent can click through and a polished multi-agent status board. If you work entirely on a Mac, it's an easy recommendation, and its native engine is quicker than ours. Where we differ is reach and contract: TermFlow runs on Windows, macOS, and Linux, and exposes a documented HTTP API and a first-party MCP server — not a CLI plus a community-maintained MCP bridge — so any agent drives it the same supported way on every OS.
Common questions.
Is cmux better on a Mac?
For a Mac-only setup, cmux is more mature and we won't pretend otherwise. TermFlow's edge is cross-platform reach and a first-party API + MCP contract that works identically on Windows, macOS, and Linux.
How does driving them actually differ?
cmux exposes a CLI and a socket, and its MCP server is a community project. TermFlow ships a documented HTTP API and a first-party MCP server, so the integration is the same supported contract everywhere.
Is TermFlow open source too?
Yes, Apache-2.0 — the full terminal, API and MCP server included, is free on your machine. See pricing.