- Compare
- vs Conductor
Plexus
Plexus and Conductor both run coding agents in parallel git worktrees. How they differ on platforms, the claude binary, review, hooks, git hosts and cloud.
Plexus and Conductor solve the same problem the same basic way: one agent per task, each in its own git worktree, managed from a desktop app. They differ in which agents they run, where those agents run, and which platforms they run on.
Side by side
Claims about Conductor are from its own documentation and site, linked on each row, and were last checked on . Conductor's website.
| Topic | Plexus | Conductor |
|---|---|---|
| Platforms | macOS (Apple Silicon and Intel), Windows x64 and Linux x86_64. Plexus docs | macOS. Conductor says it is not available for Windows or Linux yet. Source: conductor.build |
| Agents | Claude Code. Plexus docs | Claude Code, Codex, Cursor and OpenCode, in parallel. Source: conductor.build |
| The Claude Code binary | The claude you installed yourself, found on your PATH. Plexus docs | Ships its own bundled copy of Claude Code and Codex, which you should not update or modify, and adds Conductor system prompts that you can customise per repository. Source: conductor.build |
| Model access | Your existing Claude Code login. No API key. Plexus docs | Uses the auth already on your machine: a Claude Pro or Max login or an API key. Cursor sessions need a Cursor API key. Source: conductor.build |
| Where agents run | On your machine. Plexus docs | Local workspaces, plus Conductor Cloud: an isolated cloud sandbox per agent, with your repos and dependencies pre-installed, that keeps working after you close the laptop. Source: conductor.build |
| Price | The core app is free. A paid plan adds sync, team features, GitHub issues, GitHub Projects boards and Plnnrly projects inside the app, and stacks with ordered merging. Plexus docs | A free plan for local workspaces. Paid plans add Conductor Cloud, multiplayer, the Conductor API and a mobile app. See their pricing page. Source: conductor.build |
| Worktree location | Inside the project, at <project>/worktrees/<session> by default. Configurable, always under the project root. Plexus docs | A worktree per workspace, usually under ~/conductor/workspaces/<repo>/<workspace>. Source: conductor.build |
| Env files and ports | Copies a list of files into each worktree (.env and .env.local by default) and reserves a block of 10 ports per session. Plexus docs | A Files to copy setting for gitignored files, and a port range per workspace in CONDUCTOR_PORT. Source: conductor.build |
| Scripts and hooks | Create, Run and Teardown hooks at global, workspace and project level, with combine modes, plus hooks committed in .plexus/hooks.json. Plexus docs | Setup, run and archive scripts, edited in the app or in .conductor/settings.toml, which you commit to share them with teammates. Source: conductor.build |
| Review | A PR-style diff with comments sent to the agent, AI review, an unattended review-and-fix cycle, and the pull request conversation. Plexus docs | A Diff Viewer with line comments sent to the agent, and GitHub review comments shown in Conductor. Source: conductor.build |
| Before merging | PR status and aggregate CI status on every session. Plexus docs | A Checks tab that gathers git status, PR metadata, CI checks, deployments, GitHub comments and todos, and can block or discourage a merge while work is open. Source: conductor.build |
| Git hosts | GitHub and Bitbucket, with a one-click sign-in. The gh CLI is not needed. Plexus docs | Setup requires GitHub authentication in the terminal (gh auth status). Source: conductor.build |
| Issue trackers | GitHub issues, GitHub Projects boards and Plnnrly projects (backlog, board and sprints) as tabs in the app, on a paid plan. Start a session from any issue or work item, linked to it. Plexus docs | Create a workspace from a GitHub or Linear issue, and the agent inherits the issue's title, description and context. Source: conductor.build |
| Team features | Organization workspaces, managed settings and a shared prompt library, on paid seats. Plexus docs | Multiplayer and live collaboration on paid plans, and an admin portal on Teams. Source: conductor.build |
- You are on a Mac and want several agent vendors in one app. Conductor runs Claude Code, Codex, Cursor and OpenCode side by side.
- You want agents to keep working in the cloud. Conductor Cloud runs agents in sandboxes after you close the laptop, and on paid plans teammates can follow the same workspace and contribute to its chat.
- Your team works in Linear, or wants a pre-merge checklist. Conductor starts workspaces from Linear issues, and its Checks tab collects CI, deployments, review threads and todos before a merge.
- You are on Windows or Linux. Conductor does not support them yet.
- You want the
claudeyou installed, unmodified. Plexus runs the binary on yourPATHwith your own configuration and login, rather than a bundled copy. - You want everything to run locally. Agents run on your machine, and the core app needs no plan.
- You plan in GitHub Projects or Plnnrly. A repository's issues, a GitHub Projects board or a Plnnrly project's backlog, board and sprints sit in a tab, each item a click away from a session linked to it (paid plan).
- You use Bitbucket. Plexus opens and tracks pull requests on GitHub and Bitbucket without the
ghCLI. - You work across many repositories. A workspace, project and session tree, a dashboard of every session's state, a git client with a commit graph, hooks that cascade from global to project, and an unattended review-and-fix cycle in the diff view.
Conductor ships often. The rows above were checked against Conductor's own docs and pricing page on the date shown; follow the source links for the current state.
Try it on
Plexus is free to download for macOS, Windows and Linux. It runs the Claude Code you already have, with your existing login.