Conductor is shutting down: the dates, how to keep your work, and what to use next

Conductor announced on 4 November 2026 that it is joining Meta and winding the product down. Conductor Cloud goes read-only on 13 November and shuts down on 20 November, when Conductor begins deleting Cloud data, so move or export cloud workspaces before then. Local Conductor keeps working and gets new models and critical fixes until early 2027, and because every local workspace is an ordinary Git branch in a worktree, any tool that works with Git can pick your work up.

The dates, from Conductor's own announcement

The announcement also says the team hopes to have something new to use early next year. It does not say what, or whether Conductor workspaces will carry over to it, so plan as if they will not.

If you use Conductor Cloud, move or export before 20 November

Cloud workspaces run in hosted sandboxes, and Conductor stores their chats on its servers. Conductor begins deleting both on 20 November. Conductor gives you two ways to keep them:

1. Transfer to local. Right-click a cloud workspace and choose Transfer to local. This moves the workspace and its chats to your Mac, where local Conductor keeps running.
2. Export data. Go to Settings, Account, Export data to download an archive of all your Conductor data. This works after 13 November too, while Cloud is read-only.

Cloud workspaces only support GitHub repositories, so any branch an agent already pushed is on GitHub and is not affected. What you can lose is work that was never pushed and the chat history behind it. Do the transfer or export before you start evaluating replacements, not after.

If you use local Conductor, your work is already plain Git

Nothing breaks for local users on 13 or 20 November. You have until early 2027, which is enough time to try other tools properly. It also helps to know what Conductor actually created on your disk, because none of it is locked into the app.

Each workspace is a Git worktree with its own branch, usually under ~/conductor/workspaces/<repo name>/<workspace name>. Worktrees share the repository's history, branches and remotes with your original checkout. To see every workspace Conductor made for a repository, run this from the repository's main checkout:

git worktree list

Each line shows a worktree's path and the branch checked out in it. For any workspace whose work you want to keep, check for uncommitted changes, commit them, and push the branch:

cd ~/conductor/workspaces/<repo name>/<workspace name>
git status
git add -A
git commit -m "Work from Conductor workspace"
git push -u origin HEAD

git push -u origin HEAD pushes the branch that is checked out, under the same name, and sets it to track the remote. Once a branch is pushed, any other tool or machine can pick it up. In your main checkout the branch already exists, but Git lets a branch be checked out in only one worktree at a time, so you can git switch to it there only after you remove the Conductor worktree.

When you no longer need a workspace, remove its worktree with Git rather than deleting the folder:

git worktree remove ~/conductor/workspaces/<repo name>/<workspace name>

Git refuses to remove a worktree with uncommitted changes or untracked files unless you add --force, which protects work you forgot to commit. The branch itself stays in the repository. Cleaning up leftover worktrees covers the same commands in more detail.

Keep the settings and the chats

Two other things are worth carrying over.

• Setup scripts. If you configured Conductor, the commands live in .conductor/settings.toml or .conductor/settings.local.toml in your repository, in ~/.conductor/settings.toml, or in Conductor's own Settings, with the setup command under scripts.setup. Conductor's docs tell you to gitignore settings.local.toml, so pushing a branch does not carry it; copy it by hand. That is the command any replacement needs to run in a fresh worktree. Conductor's Files to copy setting uses .worktreeinclude-style patterns for gitignored files such as .env.local. Claude Code reads a .worktreeinclude file in the same .gitignore syntax and copies matching gitignored files into the worktrees it creates with Git, so those patterns move across almost as they are.
• Chat history. Use Settings, Account, Export data for an archive of your Conductor data. Conductor's own docs say it keeps its files in ~/Library/Application Support/com.conductor.app and ~/conductor, and that Claude Code and Codex keep theirs in ~/.claude and ~/.codex. Back those folders up before you uninstall anything.

What to use instead depends on which part of Conductor you relied on

Conductor combined several things: a worktree per task, a review and pull request flow, hosted cloud sandboxes, and a single window over many agents. No single replacement covers the same mix, so start from the part you would miss most.

Prices were read on each vendor's site on 11 November 2026.

The closest match: Paradev

Paradev, formerly Superset, works the way Conductor did. Each task gets its own Git worktree and branch, and you watch, review and merge from one window. It runs Claude Code, Codex and other command-line agents. The desktop app runs on macOS, with an experimental Linux build and no Windows build yet. The free plan covers one user with local workspaces, the desktop app and the CLI. Pro costs $20 per user a month, or $16 billed yearly, and Team costs $60 per user a month and adds cloud workspaces. The code is on GitHub under the MIT licence, which matters more than usual after watching a tool you depend on wind down. Paradev and its alternatives compares it in more depth.

Open source on every platform: Emdash Classic

Emdash Classic is an open-source desktop app for macOS, Windows and Linux that runs parallel tasks in separate Git worktrees and can run agents on remote machines over SSH. Read its status before you move to it: Emdash says Classic stays available and keeps getting fixes, but new development has moved to Emdash 2.0, a cloud product for teams that is in early access. Because Classic is open source, you can keep using and building it whatever happens to the company, but you are choosing a tool in maintenance.

No new app at all: Claude Code's own worktrees

If you used Conductor mainly to run Claude Code, Claude Code now does the core of it. In the Claude desktop app you can run several sessions in parallel and turn on Worktree so a session runs in its own Git worktree. In a terminal, this creates a worktree under .claude/worktrees/feature-auth/ on a new branch named worktree-feature-auth and starts Claude in it:

claude --worktree feature-auth

With claude --worktree in a terminal you give up a single view across agents and a review screen. The desktop app gives you a session list and a diff view, but only for Claude Code. Either way there is nothing to pay for beyond your Claude plan. Running multiple Claude Code agents at once covers this setup end to end, and running multiple Codex CLI agents covers the equivalent for Codex.

A terminal built for agents: cmux

cmux is a free, open-source native macOS terminal built on Ghostty. Vertical tabs show each workspace's branch, directory and ports, and a ring lights up around a pane when an agent needs attention. It is a terminal, so worktrees and pull requests are up to you or your agent: pair it with claude --worktree or your own git worktree commands. Its paid Pro plan adds cloud agents on remote VMs, which makes it one of the few options here for Conductor Cloud users who want agents to keep running away from their Mac.

Where Armadai fits

Armadai is a different shape from Conductor. Conductor organised work as workspaces, one branch each, listed in a sidebar. Armadai is a native macOS app that puts many projects on one infinite canvas: each project folder becomes a workspace with its own Claude Code, Codex, Grok or Cursor agents, terminals, code editor, browser, notes and task boards. A sidebar shows which sessions across every project are working, idle or waiting for approval, and for most requests you can approve from there without switching to that project.

The part closest to Conductor's workflow is task hand-off. You choose Run with Claude or Run with Codex on a task, Armadai gives that run its own Git worktree, and successful work comes back as a draft pull request for you to review. You open your repository folder as a workspace; to bring Conductor work across, push or check out the branches you want to keep, as above.

Be clear about what it does not replace. Armadai runs on your Mac, not in hosted sandboxes, so it is not a substitute for Conductor Cloud: terminals and command-line agents can keep running after you quit the app if you enable the background session helper and choose Keep Running and Quit, but Codex Agent and IDE tiles still close, and nothing survives logging out or shutting the Mac down. It runs only on macOS and has no free plan. It costs $20 a month or $120 a year after a 7-day free trial that needs no card, and it needs macOS 14 or later on Apple Silicon and Intel Macs. Choose it if what you want from a Conductor replacement is a view of several projects and their agents at once, rather than a closer copy of Conductor. Armadai vs Conductor compares the two directly, and plan details are under pricing.