Conductor

Desktop app for running multiple Claude Code and Codex agents in parallel git worktrees.

Recommended for managing several Claude Code and Codex agents at once in parallel git worktrees,1234 with some commenters calling it their daily driver or adopting it across a team.5678 Complaints vary rather than converge: some found its UX cluttered or clunky,91011 and one disliked that it runs agents directly on the host instead of in a sandbox.12
The HN verdict, written from 12 cited comments
11recommend
3warn against
Feb 13, 2026first mention
Oct 1, 2026latest mention
Nov 25 – Oct 26
Used forfor parallel agent workflowsfor Claude Code and Codex usersfor teamsrunning coding agentsworkflow orchestration

Why people recommend it

Parallel worktrees · 3

Runs multiple coding agents side by side, each in its own git worktree.

“The best at that that I've found is Conductor”

“Then use Conductor for worktrees w/ Claude/Codex for mid-size tasks and code review.”

Show 1 more

“Use cmux or conductor to manage multiple instances of Claude Code”

Daily driver · 3

Several commenters use it as their main tool for agentic coding.

“I use Claude Opus 4.8 + Conductor as my daily driver”

“I use Conductor pretty much exclusively and it makes it incredibly easy to try different models”

switched from Claude Codeon “GPT-5.6”
Show 1 more

Team productivity · 3

Teams report heavy use, with one dropping Cursor seats for it.

“my team and I are very heavy users of https://www.conductor.build .”

team lead, heavy agent userswitched from Cursoron “Cursor 3”

“we've loved using Conductor here at Digits. I've been using it since February”

Show 1 more

“Engineers use Conductor, stacked PRs, Linear, and multiple frontier models every day”

Model switching · 1

Makes it easy to try different models, even within one workspace.

“I use Conductor pretty much exclusively and it makes it incredibly easy to try different models”

switched from Claude Codeon “GPT-5.6”

Lifecycle hooks · 1

Worktree setup and teardown hooks allow isolated databases and config per task.

“The best at that that I've found is Conductor”

Caveats and dissent

Cluttered UX · 2

Some found the interface clunky or disliked its text rendering.

“I really didn't like the extra stuff conductor added to the UX (the text rendering always drove me nuts).”

“I also use https://conductor.build/ and GitHub but this is starting to feel clunky”

Underwhelming · 1

One commenter tried it and was not impressed.

No sandboxing · 1

Agents run directly on the host machine rather than in a sandbox.

“was not very jazzed about the fact that it was running the agents directly on the host”

Backend lock-in · 1

It works with Claude and Codex backends, so a Copilot-only workplace could not use it.

“The best at that that I've found is Conductor”

Remote and performance · 1

One user switched to another tool for remote SSH support and better performance.

“we've loved using Conductor here at Digits. I've been using it since February”

GUI over terminal · 2

Terminal-focused users built alternatives that fit tools like tmux, neovim and lazygit.

“born out of using Conductor and similar tools but preferring to work in the terminal”

“I prefer to run sessions for the same project serially, working on main, rather than in parallel like how Conductor does with the help of worktrees.”

Often compared with

Who recommends it in their own words

From the makers not counted in the ranking

“I'm biased (I'm the creator) but I use Conductor every day.”

All comments 24

“I usually recommend Conductor to most people.”

built their own agent multiplexeron “Pi 1.0”

“Engineers use Conductor, stacked PRs, Linear, and multiple frontier models every day”

“The open source continues to live:”

“Initially I was doing parallel coding sessions with Conductor.”

“I use Conductor pretty much exclusively and it makes it incredibly easy to try different models”

switched from Claude Codeon “GPT-5.6”

“was not very jazzed about the fact that it was running the agents directly on the host”

“I use a mix of Conductor and Repoprompt!”

“born out of using Conductor and similar tools but preferring to work in the terminal”

“I prefer to run sessions for the same project serially, working on main, rather than in parallel like how Conductor does with the help of worktrees.”

“Use cmux or conductor to manage multiple instances of Claude Code”

“we've loved using Conductor here at Digits. I've been using it since February”

“Then use Conductor for worktrees w/ Claude/Codex for mid-size tasks and code review.”

“I use Claude Opus 4.8 + Conductor as my daily driver”

“give conductor a try. runs with sqlite or if you want to run it on a server mysql or postgres.”

“I really didn't like the extra stuff conductor added to the UX (the text rendering always drove me nuts).”

“I also use https://conductor.build/ and GitHub but this is starting to feel clunky”

“The best at that that I've found is Conductor”

“my team and I are very heavy users of https://www.conductor.build .”

team lead, heavy agent userswitched from Cursoron “Cursor 3”

“I love Conductor on my Mac”

“sitting in Claude / https://www.conductor.build”

Threads where it came up

Data: conductor.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.

Keyboard shortcuts
j / kNext / previous item
o or EnterOpen selected item
/Search
g hHome
g tTop
g rRising
g cCategories
tToggle dark mode
?This help