Checked on 2026-09-29
DMN and Superset
Superset is built to orchestrate lots of CLI agents at once, each in its own git worktree. DMN runs agents side by side too, on Windows, and adds an engine they share.
At a glance
| Superset | DMN | |
|---|---|---|
| Where it runs | The Mac; Linux in beta; remote hosts | Windows, on your machine (Mac and Linux planned) |
| Agents | Claude Code, Codex and any CLI agent | Claude Code and Codex side by side, plus shells |
| Keeping agents apart | A git worktree for each agent | File claims in one checkout, or a git worktree each |
| Its MCP server | Orchestration: tasks, workspaces, terminals | Code intelligence: search, callers, impact, memory, claims |
| Memory across agents | — | Notes every agent on the project reads and writes |
| Source | Source-available (Elastic License 2.0) | Not public yet |
| Price | Free for one person; paid per user | Free |
The Superset column is from superset.sh on 2026-09-29. "—" means we didn't find it there.
Which should you use?
Superset if you're on a Mac and want to orchestrate a large number of agents, each on its own branch, or run them on remote machines.
DMN if you're on Windows, or want your agents to share what they learn, see who's editing what in one checkout, and spend fewer tokens finding code. How we measured the saving.
Questions
Do the two MCP servers do the same thing?
No. Superset's lets an agent manage tasks, workspaces and terminals. DMN's gives agents code intelligence: search that returns the code, callers and impact, shared notes and file claims.
Does DMN support worktrees?
Yes. The spawn sheet can start any agent in its own git worktree and branch, or in the project root.