The best Conductor alternatives right now are Orca if you want the closest replacement (it opens your existing Conductor workspaces in place and runs on macOS, Windows and Linux), Emdash if your tasks start as tickets in Linear, Jira or GitHub, and Claude Squad if you live in the terminal. If you only use one agent, Claude Code's --worktree flag or the worktree mode in the Codex desktop app may be all you need. There is no longer a deadline: on November 12, 2026 Conductor reversed its shutdown plan, and it shipped version 0.95.0 on November 16.
This guide is about Conductor (conductor.build), the Mac app for running Claude Code, Codex, Cursor and OpenCode side by side, not the Conductor SEO platform. It announced on November 4 that it is joining Meta. Below: what changed since, how its main competitors differ, and a migration checklist built on one useful fact: Conductor workspaces are ordinary git worktrees, so your code is never locked in.
Conductor shutdown dates, and why they no longer apply
What's new (November 18, 2026): On November 12 Conductor added "Plans have changed! We'll still be developing Conductor." to its announcement, and its FAQ now answers "Will I have to stop using Conductor?" with "Nope!". Updates did resume: the changelog lists 0.94.2 ("Conductor is back", November 13), 0.95.0 on November 16, which lets agents create workspaces and start chats with other agents, moves the app from Tauri to Electron and stores settings in the app instead of .conductor/settings.toml files (imported automatically), and 0.95.1 with GPT-6.2 models on November 17.
For the record, this is the schedule from the November 4 0.93.0 changelog entry. It no longer appears on the announcement page:
| Date | What Conductor announced on November 4 |
|---|---|
| November 4, 2026 | No new sign ups or downloads. Free users can't upgrade; Pro users keep Pro features for free. |
| November 13, 2026 | Conductor Cloud workspaces go read only and agents stop taking messages. |
| November 20, 2026 | Conductor Cloud shuts down and cloud user data starts being deleted. |
| Early 2027 | The local Mac app stops getting new models and bug fixes. |
So nothing forces a move today. The reversal was a short note rather than a new policy, so keep a copy of cloud work anyway: right click a cloud workspace and choose Transfer to local, or open Settings, Account, Export data for an archive of everything.
What to look for in a Conductor alternative
Conductor did four jobs, and the alternatives split them up differently:
- Isolation. Each task got its own git worktree: a separate folder on its own branch sharing one repository history, so two agents never edit the same file.
- Setup scripts. A setup script (in
conductor.json,.conductor/settings.toml, or since 0.95.0 the app's own settings) installed dependencies in every new workspace, a run script started the dev server, and an archive script cleaned up. Conductor also assigned each workspace a port. - Review. A diff viewer, checks and a pull request button for each workspace.
- Cloud. Conductor Cloud kept agents running while your laptop slept.
Most replacements cover the first three well; several run only on machines you own.
Conductor alternatives and competitors compared
Versions and licenses below were checked on the GitHub API on November 18, 2026.
| Tool | Runs on | License | Latest release | Best fit |
|---|---|---|---|---|
| Orca | macOS, Windows, Linux, plus iOS and Android companions | MIT | v1.4.263 (Nov 18, 2026) | Closest drop in replacement |
| Emdash | macOS, Windows, Linux | Apache 2.0 | v1.2.11 (Nov 6, 2026) | Teams that start work from issue trackers |
| Claude Squad | Terminal with tmux | AGPL 3.0 | v1.0.20 (Aug 20, 2026) | Keyboard driven terminal users |
| T3 Code | Desktop, web, iOS and Android | MIT | v0.1.10 (Nov 16, 2026) | Controlling agents from your phone |
Claude Code --worktree | Wherever Claude Code runs | Proprietary | Built in | Claude Code only users |
| Codex app worktrees | ChatGPT desktop app | Proprietary app | Built in | Codex only users |
All six use one worktree per task and run the agent CLIs you already pay for. None includes model usage, so your Claude, ChatGPT or Cursor plan still sets your limits.
Orca: the closest drop in replacement
Orca, from Stably AI, is a free MIT licensed desktop app that runs any terminal coding agent (Claude Code, Codex, Cursor CLI, OpenCode, Copilot and many more) in its own worktree. It ships macOS, Windows and Linux builds, and the repository had about 128,700 stars on November 18.
What makes it the easiest move is its migration guide for Conductor users. Orca opens Conductor workspaces where they already sit, usually under ~/conductor/workspaces/, without copying anything, so uncommitted changes stay put. Setup and archive scripts move to scripts.setup and scripts.archive in an orca.yaml file at the repo root, run actions become Quick Commands, and Orca still sets CONDUCTOR_ROOT_PATH so old scripts keep working. Two things don't carry over: Orca does not reserve a port per worktree (drop --port $CONDUCTOR_PORT), and it can't import Conductor's chat export, though it can resume sessions the agent CLIs saved on disk.
For the cloud gap, Orca has no hosted machines. Its answer is a Remote Orca Server on a Mac mini or VM you control, SSH worktrees, or sandboxes from a provider you already use. If that sounds like more work, our comparison of agent sandboxes from E2B, Daytona and Modal covers the hosted side.
Pick it if you liked Conductor's workflow and want it on any operating system with the least relearning.
Emdash: best for issue driven teams
Emdash is an Apache 2.0 desktop app from General Action (YC W26) for macOS, Windows and Linux. Each task runs in its own worktree and branch, and it detects installed agents such as Claude Code, Codex, Cursor, OpenCode, Amp and GitHub Copilot.
Its standout feature is ticket intake: you can send an issue from Linear, GitHub, Jira, GitLab, Asana and several other trackers straight into an agent, then review the diff, open a pull request and watch CI checks in the same window. Remote machines work over SSH. Per project settings, documented in Emdash's project settings page, cover setup, run and teardown scripts plus "preserve patterns" that copy gitignored files like .env into new tasks, and you can share them with a team through a committed .emdash.json file. The README says app state stays in a local SQLite database and telemetry can be switched off.
Pick it if your work starts as tickets and you want the tracker, the agents and the pull request in one place.
Claude Squad: best for the terminal
Claude Squad is a small AGPL 3.0 terminal app that runs Claude Code, Codex, Gemini CLI, Aider or any other command in separate tmux sessions, each on its own git worktree. You create sessions with n, attach with Enter, commit and push a branch with s, and pause a session with c. It needs tmux and the GitHub CLI installed.
On our Linux test box the 1.0.20 binary reported its version and printed a config with claude as the default program and auto accept turned off. Its interface needs a real terminal, as expected for a tmux tool. The last release is still 1.0.20 from August 20, 2026, though a fix was merged on November 13, so it moves slowly compared with the desktop apps.
Pick it if you already work in tmux and want the parallel workflow without a desktop app.
T3 Code: best for steering agents from your phone
T3 Code is an MIT licensed "agent harness control surface" with a desktop app, a web app and iOS and Android apps. It drives Codex, Claude Code, Cursor, OpenCode, Grok Build and others using the subscriptions already signed in on your computer. Its README warns the project is very early, so treat it as a companion to one of the tools above for now.
Built in options: Claude Code and the Codex app
If you ran only one agent in Conductor, you may not need another app.
Claude Code has worktrees built in. Running claude --worktree feature-auth (or -w) creates a worktree under .claude/worktrees/feature-auth/ on a branch named worktree-feature-auth and starts a session there. A .worktreeinclude file copies gitignored files such as .env into each new worktree, and on exit Claude asks whether to keep or remove a worktree that has changes in it. The details are in Anthropic's worktree documentation, and our guide to Claude Code background agents shows how to watch several sessions from one screen.
Codex does the same inside the ChatGPT desktop app. Choose Worktree under the composer, pick the starting branch, and Codex creates a worktree (in a detached HEAD state by default). Handoff moves a chat and its code between the worktree and your main checkout, and scheduled tasks can run on their own background worktrees, per OpenAI's Codex worktrees page. If you are still choosing between the two agents, see Claude Code vs Codex vs Gemini CLI.
What about Vibe Kanban?
Vibe Kanban appears in many lists, but its repository now opens with "Vibe Kanban is sunsetting," and its last tagged release is from April 24, 2026, so we left it out.
How to migrate from Conductor, step by step
This checklist works for any of the worktree tools above. We tested the git parts on a scratch repository.
- Push everything first. In each workspace, commit all changes including new files and push the branch. Copy gitignored files such as
.envsomewhere safe, because they never reach the remote. - Back up cloud work. Use Transfer to local for each cloud workspace you care about, then export your data.
- Find the real checkout. Inside a Conductor workspace, run
git rev-parse --path-format=absolute --git-common-dir. In our test it printed the main checkout's.gitfolder, not the workspace folder. Add that checkout, not a fresh clone, to your new tool so it can see the existing worktrees.git worktree listin that checkout shows them all. - Move your scripts. Copy the setup, run and archive commands (on 0.95.0 or later, from the repository settings in the app) into the new tool's config (
orca.yaml,.emdash.json, or a short note in your repo for Claude Code users). ReplaceCONDUCTOR_WORKSPACE_PATHwith the current directory and remove any reliance onCONDUCTOR_PORT. - Carry your secrets. A plain
git worktree adddoes not copy gitignored files. In our test the new worktree had no.envuntil we copied it. Use the tool's equivalent:.worktreeincludefor Claude Code and Orca, preserve patterns for Emdash. - Don't archive in Conductor after switching. Archiving deletes the workspace folder, which is now your new tool's worktree. Quit Conductor instead.
- Clean up last. When a workspace is finished, delete it from the new tool. If you remove a folder by hand, run
git worktree prune. In our test, deleting the folder kept the branch and its commits, but the uncommitted edit inside it was gone for good, which is why step 1 comes first.
Which Conductor alternative should you choose?
- You want Conductor back, on any OS: Orca. It is the only one with a written Conductor migration path, and it reads your workspaces in place.
- You need a Conductor alternative for Windows or Linux with ticket intake: Emdash.
- You prefer the terminal: Claude Squad, or plain
claude --worktreesessions in tmux. - You need agents running while your laptop is closed: Orca with a Remote Orca Server, or a hosted cloud agent. Check what an agent harness is if you are weighing a hosted service against running the CLIs yourself.
- You want only open source parts: Orca, Emdash, Claude Squad and T3 Code are all open source, and so are agents like OpenCode and the Codex CLI. Our list of the best open source coding agents covers the agent side.
FAQ
Is Conductor shutting down?
Not any more. Conductor announced on November 4, 2026 that it was joining Meta and would close Conductor Cloud on November 20. On November 12 it said it will keep developing Conductor, removed the shutdown banner in 0.94.2, and shipped 0.95.0 and 0.95.1 on November 16 and 17. No new end dates have been published.
Who are Conductor's main competitors?
For running several coding agents in parallel worktrees, the closest competitors are Orca, Emdash, Claude Squad and T3 Code, plus the worktree features built into Claude Code and the Codex app. Hosted agents such as Claude Code background agents compete with Conductor Cloud. If you meant Conductor the SEO and content platform, this guide does not cover it.
What is the best Conductor alternative for Windows?
Orca and Emdash both ship Windows installers, and both run the same agent CLIs Conductor did. Orca is closer to Conductor's workflow and has a migration guide; Emdash is stronger if you start tasks from Linear, Jira or GitHub issues.
Can I keep using my Conductor workspaces in another tool?
Yes. Conductor workspaces are standard git worktrees, so any worktree based tool can open them. Add the main checkout (found with git rev-parse --path-format=absolute --git-common-dir) rather than a new clone, and don't archive the workspaces in Conductor afterward, since that deletes their folders.
Can I import my Conductor chat history?
Not into Orca, according to its migration guide, and we found no tool that imports the export. Export your data anyway for your records. Chats that live in the agent's own session files on your Mac, such as Claude Code's, can often be resumed from the same worktree path.
Do Conductor alternatives cost money?
The apps covered here are free and open source, apart from the built in features of Claude Code and the Codex app, which come with those products' plans. In every case your model usage still comes from your own Claude, ChatGPT, Cursor or other subscription or API key.



