If you're already running multiple coding agents in parallel, you've probably hit the wall. Three Claude Code sessions in three terminal tabs, agents stepping on each other's files, no clean way to review what each one built. The workflow works in theory and falls apart in practice.

Superset is built for exactly this. It's an open-source IDE designed from the ground up to orchestrate multiple CLI-based coding agents in parallel, each in its own isolated git worktree.

Quick caveat before I get into it. I have real concerns about how multi-agent workflows are being adopted across the industry, especially when speed becomes the only metric. I wrote about that here. But this post isn't that conversation. This post is for the engineers and teams who are running multi-agent workflows already and want better tooling for it. Superset is that tool.

What it actually does

Each agent gets its own git worktree. Same repo, same history, separate working directory, separate branch. Agent A modifying a file does not affect Agent B. They cannot collide because they are not in the same place. When you're ready, you merge what you want and discard what you don't.

A unified dashboard shows every active agent, what it's touching, and notifies you when one needs your attention. No more flipping between terminal tabs hunting for activity.

The built-in diff viewer is the part I didn't expect to like as much as I do. Side-by-side, syntax highlighted, every agent's changes in one place. You can actually review what got built before it merges.

It's agent-agnostic. Claude Code, Codex, Cursor Agent, Gemini CLI, GitHub Copilot, OpenCode. Whatever you already use, Superset orchestrates around it. Your keys, your models, your providers. Local-first.

The setup that matters

Drop a setup script in your repo at .superset/setup.sh:

#!/bin/bash
# .superset/setup.sh
cp ../.env .env
bun install
echo "Workspace ready!"

Now every new agent workspace gets a clean, configured environment automatically. Dependencies installed, env vars copied, ready to go. This is the kind of thing you'd build yourself eventually. Superset just makes it the default.

Open source, and actually active

This part matters. Superset isn't a closed-source SaaS with a free tier. The full source lives on GitHub under Apache 2.0. You can read it, fork it, contribute to it, or run your own build.

The repo is one of the more active developer-tool projects I've watched recently. Over 10k stars, 50+ contributors, 100+ releases, 1000+ commits. The team ships constantly. Open issues get triaged fast. PRs get reviewed and merged on real timelines, not the "we'll get to it eventually" pace a lot of open-source projects fall into.

The Discord is good too. Engineers actually using the tool, not just lurkers. The founding team (Avi, Kiet, and Satya) shows up there directly. I've seen feature requests turn into shipped code in days. That kind of responsiveness is rare and worth supporting.

If you're going to bet on a tool for your daily workflow, you want one where the team is reachable and the project is moving. Superset is both.

The gotcha

The git worktree model is the whole game. If you've never worked with worktrees before, the mental shift is small but real. Each agent is in its own directory at its own branch. Changes don't propagate until you merge. You stop thinking about agents as sessions and start thinking about them as parallel branches with someone else doing the work.

Once that clicks, the tool gets out of your way. Which is what you want from an IDE.

One-click handoff to your editor is the other thing worth flagging. VS Code, Cursor, Xcode, JetBrains. Open any worktree where you actually want to work on it. The orchestration layer doesn't try to replace your editor, it just feeds it cleanly.

Wrap

If you're running multi-agent workflows, you should be running them in Superset. The worktree isolation, the diff viewer, and the velocity of the project itself are all reasons to install it today. Star the repo, join the Discord, follow the team on X.

What are you running it with? Drop your setup in the comments.

Mentioned in this post:

• Superset by @superset_sh — ⭐ the repo, follow the team on X
• Superset team: @avimakesrobots, @flyakiet, @saddle_paddle — give the founders a follow

More from me:

• 🐦 Follow on X: @passandscore
• 📬 Longer takes: jasonschwarz.xyz