Mac and Windows
Conductor app on Mac, and the same idea on Windows
Updated November 17, 20268 min read
The Conductor app, from conductor.build, runs several coding agents at once on your Mac, each in its own isolated workspace, and helps you review and merge what they did. As of November 2026 it is Mac only, with no Windows or Linux version. The good news is that its core idea is built on plain git, so Windows users can get the same parallel workflow with other tools, and this page shows how.
What the Conductor app gets right
Knowing what Conductor does well tells you what to look for in any replacement. Its makers describe it as a way to run Claude Code, Codex and Cursor agents in parallel, and its docs add OpenCode too.
One workspace per task
Each task gets its own workspace with its own branch, files, terminal, diff and review path. Agents can't trip over each other.
Built on git worktrees
Each workspace is a git worktree (a second copy of your project folder that git keeps linked to the same history).
Setup scripts
You can tell Conductor what to run when a workspace is created, such as installing packages, so each copy is ready to use.
A review screen
A diff viewer shows exactly what changed before you accept it.
Checks before merging
A Checks tab gathers git status, pull request info, CI results (automatic checks that run on each change), deployments and review comments in one place as a last pass.
Start to finish in one window
Review the diff, open a pull request, merge, then archive the workspace without leaving the app.
Conductor on Mac, and why there is no Conductor for Windows yet
Conductor's website and docs only talk about Mac. The homepage says it runs agents "on your Mac" and the getting started page says to get it running on your Mac. We found no Windows or Linux download as of November 2026, and no public date for one.
People often search for "conductor build" because the website lives at conductor.build. It is the same product. If you are on a Mac and only use Claude Code, Codex, Cursor or OpenCode, it is a strong choice and you may not need an alternative at all.
If you are on Windows, you need another tool that gives you the same three things: separate copies of the project per agent, a way to see all agents at once, and a way to review and merge.
How Conductor works with Claude Code
Conductor doesn't contain its own AI. It runs the Claude Code you already have, signed in with your own Claude plan (Pro, Max, Ultra or Team). When you create a workspace, Conductor makes a new branch and worktree, then starts Claude Code inside it. You chat with that Claude Code as normal. When it is done, you look at the diff and decide.
That means the Conductor Claude Code setup has the same limits as Claude Code itself. Five agents running at once will use up your plan much faster than one. Keep an eye on usage, and give each agent a clear, separate task. Our guide to Claude Code worktrees explains the git side in more detail.
Tasks that run well side by side
- Separate parts of the app. A footer change and a database fix rarely touch the same files.
- Fixes with a clear test. "The login button does nothing on mobile" is easy to check when it comes back.
- Research or review jobs. Ask one agent to read the code and list problems without changing anything.
Avoid giving two agents jobs in the same file, like two changes to one big settings page. Both will finish, but merging them can mean picking lines by hand.
Conductor alternatives by platform and feature
| Feature | Conductor | VibeCodingDeck | Claude desktop app (Code tab) | Claude Squad |
|---|---|---|---|---|
| Mac | Yes | Yes, Apple silicon | Yes | Yes |
| Windows | No | Yes, Windows 10/11 | Yes, x64 and ARM64 | Via WSL; native build has an open bug |
| Linux | No | No | Beta | Yes |
| Agents | Claude Code, Codex, Cursor, OpenCode | Claude Code, Codex, Gemini, Copilot, Antigravity, Grok, Qwen, Kimi | Claude Code only | Claude Code, Codex, Gemini, Aider and others |
| Separate copy per agent | Worktree per workspace | Optional safe copy (worktree) | Optional worktree, off by default | Worktree per session |
| See agents at once | Workspace list | Grid of up to 12 panes | Sidebar of sessions | List, one at a time |
| Alerts when an agent waits | Not stated | Status light and three alert sounds | Notification when a task finishes | Not in its README |
| Interface | Desktop app | Desktop app | Desktop app | Terminal (tmux) |
Feature details for Conductor come from its website and docs; anything they don't mention is marked "Not stated". All entries are as of November 2026.
The Claude desktop app is the easiest free extra if you only use Claude Code: press Ctrl+N for a new parallel session and turn on Worktree before you start. Claude Squad is free but lives in a terminal; see our Claude Squad page for the Windows catch. VibeCodingDeck is the one built around watching many agents from different companies at once, and it costs $29 a month.
Parallel agents on worktrees, step by step on Windows
Here is the Conductor workflow rebuilt on a Windows PC. We use VibeCodingDeck for the grid and alerts, but steps 1, 2 and 6 are the same with any tool.
- 1
Install Git for Windows
Worktrees are a git feature, so you need git. Download Git for Windows from git-scm.com and accept the defaults. Open PowerShell and type git --version to check it worked.
- 2
Install and sign in to your agents
Install Claude Code with the PowerShell command from Anthropic, then run claude once to sign in. Add Codex or another agent if you want a second one. See Claude Code on Windows and Codex on Windows for help.
- 3
Make sure your project is a git repository
Open your project folder and run git status. If it says "not a git repository", run git init and make a first commit so there is something to copy.
- 4
Open the project and start one agent per pane
In VibeCodingDeck, add the project and open as many panes as you have tasks. Two or three is a good start. Each pane can run a different AI.
- 5
Turn on a safe copy for each agent
A safe copy is VibeCodingDeck's name for a worktree. Each agent then works in its own copy, the same way Conductor gives each task its own workspace.
- 6
Give each agent one clear task
For example: one adds a contact form, one fixes the mobile menu, one writes tests for the login page. Keep tasks in different parts of the app so the merges stay simple.
- 7
Wait for the alerts
Each pane's status light shows working, idle, waiting or done, and a sound plays when one needs you. You can jump straight to the waiting agent.
- 8
Review, merge, then clean up
Look over each agent's changes, run the app, and merge the good work back into your main project. Then remove the copies you no longer need.
If you prefer to see how the pieces fit before using an app, our page on running several Claude Code agents covers it, and Claude Code on Windows has the full install walk-through.
The same thing with plain git commands
Every tool on this page, Conductor included, is doing roughly this under the hood. You can do it yourself in PowerShell or Git Bash. Run these from inside your project folder:
git worktree add ../myapp-contact-form -b contact-form
git worktree add ../myapp-mobile-menu -b mobile-menu
git worktree listEach command makes a new folder next to your project with its own branch. Open a separate terminal in each folder and start an agent there with claude or codex. When the work is done, merge the branch back like any other branch, then remove the folder:
git merge contact-form
git worktree remove ../myapp-contact-formThis works well for two or three agents. Past that, the hard part is remembering which terminal belongs to which folder and which one is waiting for you, which is the job tools like Conductor and VibeCodingDeck take off your hands.
Windows snags to expect, and how to fix them
- "fatal: not a git repository". You ran a worktree command outside your project. Use
cdto move into the project folder first. - Each copy needs its own packages. A new worktree doesn't include the node_modules folder. Run your install command (for example
npm install) inside each copy. Conductor handles this with setup scripts; elsewhere, ask the agent to do it as its first step. - Two dev servers fight over one port. If two copies both try to start on the same address, the second fails. Give each copy a different port, or run only one preview at a time.
- "already checked out" errors. Git lets a branch live in only one worktree at a time. Make a new branch for each copy.
- Long file paths. Deep folders can hit Windows path limits. Keep worktrees close to the drive root, such as C:\code.
- Usage runs out early. Several agents share one plan. Start with two, watch your usage, then add more.
- Agent can't find git. If Claude Code says git is missing right after you installed it, close and reopen the terminal so it picks up the new install.
- Merge conflicts. If two agents changed the same lines, git stops and marks the clash in the file. Ask one of the agents to resolve it and explain what it kept.
If you hit an error that isn't on this list, copy the whole message into one of your agents and ask: "What does this mean, and what is the safest fix?" Agents are good at reading git errors, and they can usually run the fix for you once you agree.
Conductor questions from Windows users
Is there a Conductor app for Windows?
+
Not as of November 2026. Conductor's site and docs only mention Mac. Windows users can get the same workflow with VibeCodingDeck, the Claude desktop app's Code tab, or plain git worktrees.
What is conductor.build?
+
It is the website for Conductor, a Mac app that runs several coding agents in parallel, each in its own git worktree, with a diff viewer, checks and pull requests built in.
Does Conductor include its own AI?
+
No. It runs agents you already have, such as Claude Code and Codex, using your own subscriptions.
Which agents does Conductor support?
+
Its homepage lists Claude Code, Codex and Cursor, and its docs also mention OpenCode. Gemini, Copilot and others are not listed.
Do I need git to run parallel agents?
+
For separate copies of your project, yes. Worktrees are a git feature. On Windows, install Git for Windows first.
Sources
Run up to 12 AI coding agents in one window.
Claude Code, Codex, Gemini, Grok and more, side by side. Windows and Mac. From $29 a month.
Get startedKeep reading
Parallel agents
How to run multiple Claude Code agents at once: four ways, easiest last
Git first, agents second
Claude Code worktrees, starting with plain git worktree
Windows install guide
Claude Code Windows install: choose your method, then get it running
Windows walk-through
Claude Squad on Windows: what works, what breaks, what else to try
Explainer
AI agent orchestration for coding: the words, the patterns and a worked example