cmux rebuilds the terminal so agents can't slip past you
cmux, from manaflow-ai, is a native macOS terminal built for the specific moment you are running five Claude Code sessions at once and lose track of which one is sitting there waiting on you. It is built on Ghostty, written in Swift and AppKit, GPU accelerated, no Electron. The headline trick is dead simple and genuinely useful: panes get a blue ring and tabs light up the instant a coding agent needs your attention. The sidebar carries per-tab metadata, git branch, PR status, open ports, working directory. There is a built-in scriptable browser the agent can drive, SSH for remote workspaces, and full session restore. It is climbing GitHub trending at 634 stars a day.
What makes it different from the orchestrator pile. Everyone else right now, Emdash, Superset, KanBots, builds a layer on top to herd a swarm of agents. cmux goes the other direction, underneath. It rebuilds the terminal itself as the substrate and calls itself a primitive, not a solution. When you actually run agents in parallel, the hard problem is not spawning them, anyone can fork a process. The hard problem is noticing which one stalled, which one is waiting for a yes, which one quietly finished. cmux makes the terminal answer that question for you.
Why I think the angle is right. The parallel-agent space has gotten crowded fast, and most entrants are some flavor of dashboard sitting above your tools. cmux is a bet that the place to solve attention is lower down, in the thing you already live in all day. Rebuild the terminal once and every agent workflow you layer on top inherits the awareness for free.
The takeaway. As agents go from one-at-a-time to many-at-once, the bottleneck shifts from capability to your own attention, and whoever owns the surface where you notice things owns the workflow. Repo at https://github.com/manaflow-ai/cmux
← Back to all articles
What makes it different from the orchestrator pile. Everyone else right now, Emdash, Superset, KanBots, builds a layer on top to herd a swarm of agents. cmux goes the other direction, underneath. It rebuilds the terminal itself as the substrate and calls itself a primitive, not a solution. When you actually run agents in parallel, the hard problem is not spawning them, anyone can fork a process. The hard problem is noticing which one stalled, which one is waiting for a yes, which one quietly finished. cmux makes the terminal answer that question for you.
Why I think the angle is right. The parallel-agent space has gotten crowded fast, and most entrants are some flavor of dashboard sitting above your tools. cmux is a bet that the place to solve attention is lower down, in the thing you already live in all day. Rebuild the terminal once and every agent workflow you layer on top inherits the awareness for free.
The takeaway. As agents go from one-at-a-time to many-at-once, the bottleneck shifts from capability to your own attention, and whoever owns the surface where you notice things owns the workflow. Repo at https://github.com/manaflow-ai/cmux
Comments