Superset
TL;DR
Superset is a macOS desktop app from Superset, Inc. that runs Claude Code, Codex, OpenCode or any CLI agent in parallel, one git worktree per task, with built-in terminals, diff review and a browser pane. The source is under the Elastic License 2.0. It suits individual developers, with paid Pro features for remote access, mobile and automations.
Key facts
| Type | Orchestrator |
|---|---|
| Languages / SDKs | TypeScript |
| License | unknown |
| Pricing model | Open core |
| Orchestration pattern | Supervisor |
| GitHub stars | 14,764 (as of 2026-09-30) |
| GitHub forks | 1,313 |
| Last push | 2026-09-30 |
| Latest release | desktop-v1.32.0 |
| Repository | superset-sh/superset |
| Website | superset.sh |
| Documentation | docs.superset.sh |
| Last verified | 2026-09-30 |
Key features
- Each task gets a workspace: an isolated git worktree on its own branch with its own directory, terminals and detected ports. (source)
- Runs Claude Code, Codex, OpenCode, Hermes and other CLI agents; any other terminal agent works without configuration. (source)
- A
superset:orchestrateskill lets one agent (Claude Code or Codex) coordinate workers in separate workspaces through the CLI. (source) - A built-in diff viewer stages, commits and pushes changes, and the README describes selecting diff lines in a pull request and sending feedback to an agent session. (source)
- An MCP server, a
supersetCLI and a TypeScript SDK let agents and scripts create workspaces and launch agents. (source) - Terminals are backed by a background daemon, so running processes and scrollback survive app restarts. (source)
- Remote access reaches workspaces on another machine, and Automations schedule agent sessions; the pricing page places both in the Pro plan. (source)
Architecture and orchestration pattern
Pattern: Supervisor
Superset is an Electron desktop app plus a superset CLI, a TypeScript SDK and an MCP server, all backed by the same host service. A project is a git repository; a workspace is a worktree of it on its own branch, with its own terminals and ports. Sessions offer a scratch folder with no project. Terminals run under a background daemon.
Agents are the user's own CLIs running in those terminals. Superset wraps launch commands and installs lifecycle hooks in the agent configs to show status and send notifications, and its docs say it never touches model traffic. A built-in chat pane can talk to models directly when you connect provider keys.
Coordination is manual by default and optionally agent-driven: the orchestrate skill has a coordinator create a workspace and agent per worker with superset workspaces create and superset agents create, watch them with superset terminals read, and verify their structured completion messages before integrating. Results return as one branch and pull request per worker. Remote hosts connect through a relay that is off by default.
Human in the loop
A person reviews each worker's changes in the Changes panel or pull request view, can comment on diff lines and send the feedback to a running or new agent, and decides when to commit, push or merge. Agents ask for permission through their own CLIs, and the built-in chat has inline tool approvals and plan review. Sidebar status, chimes and dock badges show when an agent needs attention. The docs say to use the orchestrate skill only when fan-out is mechanical; for step-by-step review, run separate workstreams.
Harnesses it can drive
- Claude Code (evidence)
- Codex (evidence)
- OpenCode (evidence)
- Hermes (evidence)
Protocols
| Protocol | Support | Note |
|---|---|---|
| MCP | Yes evidence | Superset hosts an MCP server (https://api.superset.sh/mcp) whose tools list and create tasks, workspaces, agent sessions, terminals, pages and automations; the docs show setup for Claude Code, Codex, OpenCode and others. Server side. |
| A2A | Unknown | Searched the README, the docs full-text bundle (llms-full.txt) and GitHub code search for 'a2a' and 'agent2agent'; nothing found. Agent coordination goes through the CLI or MCP tools. |
| AG-UI | Unknown | Searched the README and docs full-text bundle for 'ag-ui'; nothing found. |
Best for
- Running several Claude Code, Codex or OpenCode agents in parallel worktrees on a Mac, with diff review and browser previews in one window. (shortlist)
- Racing the same prompt across different agents in separate workspaces and keeping the best branch. (shortlist)
- Having a lead agent fan a mechanical refactor out to workers through the orchestrate skill or MCP tools. (shortlist)
- Scheduling recurring agent runs, such as overnight audits, and reaching another machine's workspaces remotely (Pro).
Not for
- Windows users: the docs say Windows is not yet available and Linux is experimental.
- Anyone who needs an OSI-approved open-source license or wants to offer the software as a hosted service; the Elastic License 2.0 forbids the latter.
- Web-only workflows: the FAQ says there is no supported web dashboard.
Quickstart
Download the macOS app from https://github.com/superset-sh/superset/releases/latest (CLI only: brew install superset-sh/tap/superset) # Desktop app: download the .dmg from the releases page (Git required, gh optional).
# The app ships the CLI; standalone install:
brew install superset-sh/tap/superset
superset auth login
# Project-less session with an agent
superset workspaces create --session --local --agent claude --prompt "Explain the build setup"
# Worktree workspace for a project, then a Codex agent in it
superset workspaces create --project prj_... --name "fix-login-bug" --branch fix/login-bug --local
superset agents create --workspace ws_... --agent codex --prompt "Review this diff"
# Watch and steer
superset terminals read --workspace ws_... --terminal term_... --max-lines 240
superset terminals send --workspace ws_... --terminal term_... --text "also add tests"
Common pitfalls
- macOS (Apple Silicon or Intel) is the supported target; the Linux AppImage is experimental and Windows is not available.
- Every project must be a git repository; one branch maps to one workspace.
- Git is required; the GitHub CLI (
gh) is optional but needed for PR workflows. - The CLI is marked Beta: commands and flags may change, and it needs
superset auth login(or an API key in CI). - Superset installs lifecycle hooks and command wrappers under
~/.superset/binand in agent configs; removing them disables status and notifications. - Remote access relay is off by default, and remote hosts show offline until it is enabled. Mobile needs Superset Pro, iOS 26 or later, and Remote Access.
- GitHub and Google sign-ins create separate accounts even with the same email.
Pros
- Worktree-per-workspace isolation with per-workspace ports, so parallel agents and dev servers do not collide. (source)
- Does not touch model traffic: prompts and tokens go from the agent CLI to your provider on your own accounts. (source)
- Several control surfaces over one backend: desktop app, CLI, TypeScript SDK and MCP server. (source)
- Documented orchestration and race-the-agents recipes, with review through one branch and PR per worker. (source)
- The README promises the desktop app stays free and running agents in parallel on your own machine will not require payment. (source)
Cons
- Licensed under the Elastic License 2.0 (source-available, not OSI open source); it bars offering the software as a hosted or managed service. (source)
- macOS is the supported target; Linux is experimental and Windows is not available (an open request tracks native Windows). (source)
- Remote access, mobile and automations are Pro features; the pricing page lists Free, Pro and Enterprise plans. (source)
- Superset adds hooks and command wrappers to agent configs to provide status; removing them turns those features off. (source)
- The CLI is labelled Beta, so commands and flags may still change. (source)
Alternatives
FAQ
Does Superset support MCP?
Yes, as a server. The MCP server at api.superset.sh/mcp lets agents manage tasks, workspaces, agent sessions, terminals, pages and automations. The docs give setup commands for Claude Code, Codex, OpenCode and other CLIs.
What license is it under?
GitHub reports no recognized license. The repository's LICENSE.md is the Elastic License 2.0, which allows use, modification and self-hosting for your team but not offering Superset itself as a hosted or managed service.
Is Superset free?
The desktop app and local parallel workspaces are free, per the README. The pricing page lists Free, Pro and Enterprise plans, and remote access, mobile and automations need Pro. It read $20 per user per month billed monthly or $15 billed yearly on 2026-09-30.
Which agents does it run?
Claude Code, Codex, OpenCode, Hermes, Cursor Agent, Gemini CLI, Amp and others are listed as fully supported, and any CLI agent works without configuration. OpenClaw is not in the README table.
Does it proxy my model calls?
No. The docs say Superset never touches model traffic; agent CLIs talk to your provider with your accounts. The optional built-in chat pane uses provider keys you connect.
Sources
- Superset GitHub repository
- Superset README
- Superset LICENSE.md (Elastic License 2.0)
- Superset homepage
- Superset documentation
- Docs: Workspaces
- Docs: Agent orchestration
- Docs: Diff viewer
- Docs: MCP server
- Docs: The Superset model
- Docs: Remote access
- Docs: Install
- Docs: FAQ
- Docs: CLI getting started
- Superset pricing
- Superset releases