
Getting Started with Superset — Run 10+ AI Coding Agents in Parallel
Introduction
At ZenChAIne, we have repeatedly covered cmux as a terminal of choice for the AI coding agent era.
- Getting Started with cmux — A Terminal Built for AI Coding Agents
- Getting Things Done with cmux Alone — Pane Splitting, Built-in Browser, and lazygit
- Full IDE in the Terminal with Yazi + Neovim — File Trees and Code Navigation
- cmux Official Skills Deep Dive — Terminal Control, Browser Automation & Markdown Viewer
- Announcing cmux Skills for agent-skills — fork, delegate & second-opinion for Multi-Agent Orchestration
cmux is a macOS-native terminal that polishes the "terminal-first" experience of working with agents through pane splitting, native Git integration, and extensibility via official skills.
That said, the theme of "a terminal/workspace for the AI agent era" admits more than one approach. One path is to supercharge the terminal itself, as cmux does. Another is to provide an editor-like UI backed by a parallel execution substrate built on Git worktrees.
Superset, the focus of this article, takes the latter path — it is an alternative approach that complements, rather than replaces, cmux. It is a desktop application that orchestrates multiple CLI-based agents across isolated Git worktrees, and it works with Claude Code, Codex, Gemini CLI, and any other agent that runs in a terminal. Launched on Product Hunt on February 27, 2026 as #1 Product of the Day with over 500 upvotes, Superset has amassed more than 9,200 GitHub stars.
Put simply: cmux competes on "macOS-native terminal + multi-pane + skill extensibility," while Superset competes on "Git-worktree-based parallel agent execution + built-in diff editor." This is not a question of which is better — it is a welcome expansion of the options available for different use cases.
This tutorial walks you through installation, workspace setup, and practical multi-agent workflows.
Key Takeaways
- Superset runs multiple terminal-based AI agents in parallel, each in its own Git worktree
- Agents are fully isolated — no merge conflicts between concurrent tasks
- Works with Claude Code, Codex, Gemini CLI, OpenCode, and any CLI-based agent
- Keyboard-driven workflow from workspace creation to code review
Why Do Parallel Agents Need a Dedicated Editor?
A single agent in a single terminal works fine. The friction starts when you scale up.
Context switching overhead: With five terminal tabs running Claude Code, tracking "which tab is doing what" and "which agent is waiting for input" becomes a cognitive drain. As tasks multiply, management overhead eats into productive work time.
Merge conflict minefield: When multiple agents edit the same branch, conflicts become inevitable. You can manually create Git worktrees and separate branches, but managing five or ten of them by hand is unsustainable.
Fragmented review: Checking agent-generated code means opening a separate terminal for git diff or switching to VS Code. When the execution environment and review environment are disconnected, feedback loops slow down.
Superset solves these problems through "workspaces" — each workspace has its own Git worktree, and agent execution, monitoring, and review happen in a single interface.
How Is Superset Architected?
Superset is an Electron + React + TailwindCSS desktop application. Under the hood, it uses Bun as its runtime, tRPC for communication, and Drizzle ORM + Neon for data management.
Three core design principles shape the product.
1. Workspace = Git Worktree
Creating a workspace automatically generates a Git worktree. Each workspace has its own branch and file tree, eliminating file conflicts between agents.
2. Agent Agnostic
"If it runs in a terminal, it runs on Superset." Claude Code, Codex, Gemini CLI, OpenCode, Cursor Agent, Amp Code — any CLI-based agent works without vendor lock-in.
3. Zero-Config Instant Launch
Workspace creation takes one action: ⌘N (full setup) or ⌘⇧N (quick create). Enter a prompt and Superset auto-generates a branch name, runs setup scripts, and opens a terminal ready for your agent.
Installation
Superset officially supports macOS only. Windows and Linux support is listed as "coming soon" in the official documentation.
Prerequisites
| Requirement | Version |
|---|---|
| OS | macOS |
| Runtime | Bun v1.0+ |
| Git | 2.20+ |
| GitHub CLI | gh (recommended) |
Option 1: DMG Download (Recommended)
Download the latest .dmg from GitHub Releases and drag it to your Applications folder.
Option 2: Build from Source
git clone https://github.com/superset-sh/superset.git
cd superset
cp .env.example .env
bun install
bun run devIf macOS shows a security dialog on first launch, click "Open" to proceed.
Creating Your First Workspace and Running an Agent
With Superset installed, let's create a workspace and run your first agent.
Step 1: Open Your Project
Launch Superset and press ⌘⇧O to open an existing project directory. Any Git repository will be recognized as a Superset project.
Step 2: Create a Workspace
Press ⌘N to open the workspace creation dialog.
- Project: Select your repository
- Base branch: The branch to fork from (typically
main) - Workspace name: A descriptive task name (e.g.,
add-auth-endpoint) - Prompt: The task to send to your agent (optional)
When you enter a prompt, Superset auto-generates a branch name. Clicking "OK" triggers:
- Git worktree creation
- Execution of setup scripts from
.superset/config.json - Terminal launch
Step 3: Start an Agent
In the workspace terminal, launch your preferred agent.
# Claude Code
claude "Add an authentication endpoint to the API"
# Codex
codex "Implement the dashboard charts component"
# Gemini CLI
gemini "Fix the TypeScript errors in src/utils"The sidebar shows agent status as it works.
Step 4: Review Changes
When the agent finishes, press ⌘L to open the changes panel. The built-in diff viewer shows all modified files. The CodeMirror-based editor (approximately 150KB, 97% smaller than Monaco) lets you edit code directly.
If everything looks good, commit and push from the terminal, then create a PR.
Multi-Agent Parallel Workflow
Superset truly shines when running multiple agents simultaneously. Here's a practical workflow.
Assigning Parallel Tasks
Suppose you want to tackle three tasks at once:
- Add a backend API endpoint
- Implement a frontend component
- Write unit tests
Create a workspace for each task with ⌘N, then launch different agents in each terminal. Since each workspace has its own Git worktree, there are no file conflicts.
Automating Setup
If each workspace needs npm install or .env copying, automate it with .superset/config.json.
{
"setup": ["./.superset/setup.sh"],
"teardown": ["./.superset/teardown.sh"]
}#!/bin/bash
# .superset/setup.sh
cp ../.env .env
bun install
echo "Workspace ready: $SUPERSET_WORKSPACE_NAME"This runs automatically on workspace creation, so agents can start working immediately.
Navigating Between Workspaces
⌘1through⌘9: Jump directly by number⌘⌥↑/⌘⌥↓: Cycle sequentially⌘B: Click from the sidebar
Switching preserves all terminal sessions, scroll positions, split layouts, and panel states.
IDE Integration
Need to edit code in VS Code or a JetBrains IDE? Press ⌘O to open the workspace directly in your external editor. Cursor position and file selection carry over for seamless handoff.
FAQ
Q. How is Superset different from cmux?
A. cmux is a macOS-native terminal app built on Ghostty's rendering engine, focused on agent notifications and a built-in browser. Superset provides full Git worktree isolation and specializes in parallel agent orchestration. Think of cmux as a terminal for agents and Superset as an orchestrator for agents.
Q. Is Superset free?
A. Yes. Superset's source code is available on GitHub under the Elastic License 2.0 (ELv2). There's no API key proxying — you manage your own agent credentials.
Q. Does it work on Windows or Linux?
A. Currently, only macOS is officially supported. The official documentation lists Windows and Linux support as "coming soon."
Q. How is this different from AI IDEs like Cursor or Windsurf?
A. Cursor and Windsurf embed AI into the IDE itself. Superset includes a built-in CodeMirror-based editor and diff viewer, but its primary purpose is orchestrating existing CLI agents as a "meta-tool." The key advantage is freedom to mix and match any agents you prefer.
Summary
Superset directly addresses the developer need to "run as many agents as I want, simultaneously." Automatic Git worktree isolation, agent-agnostic architecture, and keyboard-centric workflows remove the bottlenecks of multi-agent development.
While cmux optimizes the terminal experience for agent interaction, Superset focuses on agent orchestration. Using both together gives you the best of both worlds — terminal comfort and parallel agent execution.
As the number of AI agents in your workflow grows, so does the importance of tools to manage them. Start by creating a single workspace and trying your daily tasks on Superset.