Checked on 2026-09-29
DMN and Conductor
Conductor made running a team of agents in isolated workspaces easy on the Mac, and now runs them in the cloud too. DMN runs them on your own Windows machine, and gives them an engine they share.
At a glance
| Conductor | DMN | |
|---|---|---|
| Where it runs | The Mac, and cloud sandboxes | Windows, on your machine (Mac and Linux planned) |
| Agents | Claude Code, Codex, Cursor's agent and others, with your own subscriptions or keys | Claude Code and Codex side by side, plus shells, with your own subscriptions |
| Keeping agents apart | An isolated workspace for each agent | File claims in one checkout, or a git worktree each: your choice per agent |
| Finding code | The agents' own tools | The agents' own tools, plus a local engine that answers in one call |
| Memory across agents | — | Notes every agent on the project reads and writes |
| Teams | Multiplayer and team plans | Built for one person running many agents |
| Price | Free for local workspaces; paid plans for cloud and teams | Free |
The Conductor column is from conductor.build on 2026-09-29. "—" means we didn't find it there.
Which should you use?
Conductor if you're on a Mac, want every agent sealed off in its own workspace, or want to run agents in the cloud and share them with a team.
DMN if you're on Windows, want your agents on your own machine, or want them to share notes, claim files and spend fewer tokens finding code. How we measured the saving.
Questions
Does DMN isolate agents the way Conductor does?
It can: the spawn sheet starts an agent in its own git worktree and branch. You can also let agents share one checkout, where claims keep them out of each other's files.
Can I use DMN's engine with agents I run in Conductor?
Not on a Mac yet: DMN runs on Windows today.