mmux vs Superset

What is Superset?

Superset describes itself as "an agentic IDE to orchestrate 100+ coding agents in parallel" [3]. It is not an agent itself: it runs CLI agents you already use, such as Claude Code, Codex, OpenCode, Gemini and Cursor Agent, with your own subscriptions or API keys, and does not proxy model calls [1]. Each task gets a workspace backed by its own git worktree and branch, with terminals, a diff viewer, an in-app browser and agent status in a sidebar [3]. Desktop and CLI releases are versioned together; this page checked v1.38.0 [4].

The desktop app is built on Electron and targets macOS, with an experimental Linux AppImage; Windows is not yet available [3]. Around it sit a superset CLI, a TypeScript SDK and a hosted MCP server that let scripts and other agents create workspaces, launch agents and read terminals [6] [7]. Pro adds remote hosts, scheduled automations, an iPhone app and Linear and Slack integrations [2].

The code is on GitHub under the Elastic License 2.0, which the site calls "not OSI-approved open source" [1]. Superset (superset.sh) is unrelated to Apache Superset, and its site says the product is "getting a new name soon" [1].

Where Superset is better

• Reviewing changes in a GUI. Superset's diff viewer lets you comment on and edit an agent's changes before committing, send PR feedback back to agents, and use a design mode for UI work [3]. mmux's diff preview is read-only and stages whole files.
• Dev server preview. Superset detects which ports each workspace listens on and opens them in an in-app browser [9]. mmux has no browser; you open localhost yourself.
• A native phone app. On Pro, the iPhone and iPad app checks on agents and reviews diffs on connected computers [3]. mmux on a phone means an SSH client and a narrow terminal layout.
• Scheduled work and integrations. Automations run agents on a schedule (issue triage, dependency bumps) and open PRs, and Pro connects Linear and Slack [1] [2]. mmux has nothing comparable.
• An SDK and MCP server. Besides the CLI, Superset ships @superset_sh/sdk for Node, Bun and Deno, and an MCP server that agents like Claude Code can add over HTTP [3] [7]. mmux offers only its CLI.
• Teams and compliance. Organizations with members, and on Enterprise SAML SSO, SCIM, audit logs and a SOC 2 Type II report [2]. mmux is a single-user tool.
• Editor hand-off and Intel Macs. Worktrees open in VS Code, Cursor, Xcode or JetBrains IDEs [1], and there are prebuilt Intel macOS builds [3].

Where mmux is better

• It runs anywhere a terminal does. mmux is a TUI, so it works the same on your laptop, a Linux server or a dev container you ssh into, with static builds for Linux arm64 and x86_64. Superset's desktop app is macOS-first, with Linux marked experimental.
• Sessions come back after a quit, crash or update. Reopening a directory restores its agents and terminals, and Claude, Codex, Pi and Grok agents resume their conversation. In Superset, "Quit Superset Completely", a restart or a logout ends the sessions [5].
• Remote work without a relay or a paid plan. Run mmux on the remote machine and attach over SSH; detach, drop the connection, reattach later. Desktop notifications travel as escape sequences on the terminal stream, so they reach the machine you are sitting at. Superset's remote access is a Pro feature that goes through a relay [2] [5].
• Local control, no account. mmux ls, read, send, wait, ask and worktree new talk to the running mmux on your machine. Superset's CLI needs superset auth login or an API key for most commands, and its MCP server is hosted at api.superset.sh [6] [7].
• Agent status without hooks. mmux reads what the agent puts on screen (progress reports, bells, approval prompts) to mark it working, ready or asking. Superset installs lifecycle hooks into each agent's config, and status only works for agents launched through Superset [8].
• One dev stack across worktrees. Starting a process in a worktree stops it in the checkout that had it first, so localhost:3000 is always the branch you last started. Superset lists ports per workspace and leaves allocation to your setup scripts [9].
• Worktrees that clean up after themselves. M merges a worktree into the branch it came from, and finished worktrees (merged or pushed, clean, idle) are removed after 30 minutes by default.
• OSI open source. mmux is GPLv3-or-later; Superset's Elastic License 2.0 is source-available.

When to use which

Moving from Superset to mmux

1. Install mmux and run mmux init in the repository.
2. Move the setup commands from .superset/config.json into worktrees.setup in mmux.yaml (a single shell line) [10]. Gitignored files like .env are copied by default; list more under worktrees.copy.
3. Turn each run command into a process. mmux has no per-worktree teardown hook; a process's stop: runs when that process stops or mmux quits, which covers a docker compose down.
4. Put your agents in ~/.mmux/config.yaml so every project gets them.
5. Where a script called superset workspaces create and launched an agent, use mmux worktree new <branch> --prompt "…", then mmux wait on the printed id.

# mmux.yaml
name: my-project
worktrees:
  setup: bun install
processes:
  - name: Dev server
    cmd: bun
    args: ["run", "dev"]
    stop: docker compose down

mmux worktree new fix-auth --prompt "fix the login bug"