Guides · Checked on 2026-10-04
Run several coding agents at once on Windows
Conductor, which gives each agent its own workspace, runs on the Mac. On Windows you can set up the same thing with git and Windows Terminal in a few minutes. Here's how, what trips people up, and what DMN adds.
1. A worktree and a tab for each agent
A git worktree is a second checkout of the same repository, on its own branch, sharing one
.git folder. Give each agent one and they can't overwrite each other's edits.
-
Make a worktree for each task
In PowerShell, from your repository:
git worktree add C:\code\myapp-auth -b agent/auth git worktree add C:\code\myapp-billing -b agent/billing
-
Open a tab in each, and start an agent
Each command opens a Windows Terminal tab in that folder. Run
claudein one andcodexin the other.wt -w 0 nt -d C:\code\myapp-auth wt -w 0 nt -d C:\code\myapp-billing
-
Set each one up
A worktree has only what git tracks. Run your install (
npm install, a new.venv) in each, and copy any.envfile across. If two agents start dev servers, give one a different port: many readPORT. -
Merge, then clean up
Review and merge each branch as you would anyone's, then remove the worktree and its branch:
git worktree remove C:\code\myapp-auth git branch -d agent/auth
If git stops with Filename too long, a deep folder such as node_modules has passed
Windows' old path limit. git config --global core.longpaths true lifts it for git.
Good for: any agent, any number of them, with nothing to install but git.
Where it stops: you check each tab to see which agent is done and which is waiting for an answer. Each starts from scratch and doesn't know what the others found, and the merge conflicts are yours.
2. Or one checkout, split by folder
Start both agents in the same folder and give them different parts of the code: one on the API, one on the front end. There's nothing to set up.
Where it stops: nothing keeps one agent out of a file the other is editing, and their uncommitted changes mix. It works best with one agent writing and the other only reading: reviewing, answering questions, running tests.
3. In DMN
DMN is a Windows app for running the agents you already use. Claude Code, Codex, Gemini CLI, Cursor's CLI and Aider each run in a pane, in a real terminal, exactly as they do anywhere else.
- A worktree in one click. + agent starts an agent in the project, a folder, or a git worktree of its own.
- Who's done. Each agent has a card in the Fleet panel: its status, what it's doing now, and the lines it has changed. A toast says when one finishes a turn.
- One checkout, if you'd rather. Agents can claim the files they're about to change, and the others see the claim before touching them. Claims are advisory: they never block a write.
- What one finds, the others get. Notes and a session-start briefing carry it across, and every agent searches one local index of your code.
DMN for Windows is coming soon.
Where it stops: it's one more app, and claims only help if the agents check them. More on the workspace, and on how DMN and Conductor compare.
Which one to use
| Worktree and tab | One checkout | DMN | |
|---|---|---|---|
| Keeps edits apart | Yes, a branch each | No | A worktree each, or claims in one checkout |
| Who's done | Check each tab | Check each tab | The Fleet panel, and a toast |
| Agents share what they find | No | No | Notes and a briefing |
| What it needs | Git and Windows Terminal | Nothing | DMN |
Agents on Windows also hit their own errors, mostly from shell quoting and paths. The fixes cover the ones we hit most, and to share what agents learn across sessions, see share context between Claude Code and Codex.