All field notes

Alternatives · 7 min read ·

Conductor is shutting down: dates and alternatives

Conductor stopped new downloads on November 4, 2026. Its Cloud shuts down November 20 and its desktop app winds down in early 2027. Here is where to move.

Is Conductor shutting down?

Yes, in stages. On November 4, 2026, Conductor announced that it is joining Meta, and the same day it stopped new sign-ups and downloads. Conductor Cloud goes read-only on November 13 and shuts down on November 20, when Conductor starts deleting cloud data. The Mac app keeps getting new models and critical bug fixes until early 2027, then winds down, and Conductor says it will delete all user data when the app shuts down.

Every Conductor fact here comes from its announcement, its 0.93.0 changelog and its docs, read on November 9, 2026. We make SwarmPane, one of the alternatives below, so weigh that part accordingly.

Conductor’s wind-down, from its own announcement
DateWhat changesWhat to do
November 4, 2026No new sign-ups or downloads. Free users can’t upgrade; Pro users keep Pro features for freeNothing breaks yet, but nobody new can install Conductor, a teammate included
November 13, 2026Conductor Cloud goes read-only: you can read old chats and export data, but not send messages. Active subscribers get a refundMove cloud workspaces to your Mac and export your data before this date
November 20, 2026Conductor Cloud shuts down and Conductor begins deleting cloud dataHave your export saved by now
Early 2027The Mac app starts winding down, and Conductor deletes user data when it shuts downMove your local work to another app before then

What should you do before November 13?

Save whatever lives only in Conductor Cloud while the cloud still takes changes:

Push every branch. Commit what you want to keep, new files included, and push. Ignored files such as .env never reach your Git host, so copy them somewhere safe yourself.

Bring cloud workspaces to your Mac. Conductor’s changelog says to right-click a cloud workspace and choose Transfer to local, which moves the workspace and its chats.

Export everything. Settings → Account → Export data downloads an archive of all your Conductor data. Keep it: once Conductor deletes its copy, the archive is the only record of those chats.

Questions about refunds or your data go to support@conductor.build, the address Conductor gives in its announcement.

Can you keep using Conductor on your Mac?

For now, yes. Conductor’s FAQ says local Conductor keeps working as normal and gets new models and critical bug fixes until early 2027, when it starts winding down. Two things change sooner: nobody new can download it, so a teammate or a second computer can’t join your setup, and whatever you build around it has to move before early 2027.

Conductor also says it hopes to have “something new you can use” by then. Nothing about it is public yet, so plan as if you are moving.

Where do your Conductor workspaces live?

On your Mac, as ordinary Git worktrees. Each workspace is a git worktree with its own branch, usually under ~/conductor/workspaces/<repo name>/<workspace name>. Run git worktree list in your main checkout to see every one with its branch. Because they are plain worktrees, any app or terminal can open them, uncommitted changes included.

The agent CLIs keep their own history as well. Claude Code saves sessions per folder, so claude --resume in a workspace’s folder usually lists the conversations you had there. Claude Code deletes old transcripts after 30 days by default (settings), so pick up the ones that matter soon.

Before you clean up: deleting a workspace folder deletes its uncommitted work. Merge or push each branch first, remove the worktree with git worktree remove <path>, and run git worktree prune once the folders are gone.

What did your Conductor setup script do?

Conductor prepares each new workspace from your project settings in .conductor/settings.toml: a setup script (often a dependency install), Run actions such as a dev server on $CONDUCTOR_PORT, and files to copy that Git ignores, such as .env.local (Conductor’s docs). Other apps don’t read that file, so note what yours does before you switch: the install command, the files it copies and the ports your servers use.

What are the best Conductor alternatives?

The apps below do Conductor’s core job: several coding agents at once, each in its own Git worktree, on your own Claude, ChatGPT or other plans. Their facts come from each one’s own site or README, checked on November 9, 2026. Our comparison of tools that run AI coding agents in parallel has more of them.

Conductor alternatives, from their own pages, checked November 9, 2026
AppPlatformsAgentsPrice or licenseGood to know
SwarmPaneMac, Windows (x64) and Linux (x64)Claude Code, Codex, Cursor Agent, OpenCode, Gemini CLI, Copilot, Devin, Hermes Agent and more$17, $29 or $50 a monthUp to 16 agents in real terminals and Limit handoff between accounts; no cloud, closed source, and we make it
OrcaMac (Apple silicon and Intel), Windows and LinuxClaude Code, Codex and any other CLI agentFree, MITChat or terminal view, remote servers and a mobile app, and a Conductor migration guide
NimbalystMac, Windows and LinuxCodex, Claude Code, OpenCode and other agentsFree, MITVisual editors for docs and diagrams, a session kanban and an iOS app; the successor to Crystal
EmdashMac, Windows and LinuxClaude Code, Codex, OpenCode, Amp and moreApache-2.0Sends tickets from Linear, GitHub or Jira to an agent, and works over SSH
Paradev, formerly SupersetMac; Linux as an experimental AppImage; no Windows yetClaude Code, Codex, OpenCode, Gemini CLI, Cursor Agent or any CLI agentFree, MIT; a Pro plan adds remote hosts, an iPhone app and automationsMac-first, like Conductor
Claude’s desktop appMac and Windows; Linux in betaClaude Code onlyComes with a paid Claude planParallel sessions, each in its own worktree if you want
Claude SquadMac and Linux terminals, on tmux; WSL on WindowsClaude Code, Codex, Gemini, AiderFree, AGPL-3.0A terminal app rather than a window

Which Conductor alternative should you pick?

Pick by what you used Conductor for:

Free and open source, close to how Conductor worked: Orca, which documents the move from Conductor step by step, Nimbalyst or Emdash. All three run on Mac, Windows and Linux. On a Mac, Paradev is another free option built for the same workflow.

Only Claude Code, or only Codex: the vendor’s own desktop app runs parallel sessions with worktrees at no extra cost. Claude’s app runs Claude Code, and the ChatGPT desktop app runs Codex.

Many different agents in one view, with usage limits in mind: SwarmPane puts up to 16 agents in one grid and moves the work to another account when one hits its limit. It is paid, and there is no cloud.

A terminal workflow on Mac or Linux: Claude Squad.

Whatever you choose, keep the habit Conductor taught: one agent per worktree, and merge one branch at a time.

How do you move from Conductor to SwarmPane?

If you choose SwarmPane, here is how Conductor’s parts map onto it:

Conductor and SwarmPane, part by part
In ConductorIn SwarmPane
A workspace: a worktree, a branch and an agentA pane with Own worktree on: its own copy of the project on its own branch, with the agent CLI in a real terminal
Files to copy and the setup scriptEach new worktree gets your ignored .env files and a clone of node_modules automatically; run any other setup command once in the pane’s terminal
Run actions and $CONDUCTOR_PORTStart your dev server in a terminal pane; SwarmPane doesn’t assign ports, so give each server its own
The diff viewer and pull requestsFiles, Git and the diff beside the panes, Undo for agents for any agent step, and gh pr create in a terminal
Claude Code, Codex, Cursor and OpenCodeThe same CLIs with your own sign-ins, plus Gemini CLI, Copilot, Grok Build, Devin, Hermes Agent and more
Conductor Cloud, multiplayer and the mobile appNothing like them: everything runs on your computer

Bring your open workspaces across

To keep working in a Conductor workspace, add its folder as a project in Code mode and open a pane on it. Nothing is copied: its branch and uncommitted changes stay where they are, and claude --resume in that pane picks up a Claude Code conversation. Quit Conductor first, so two apps never drive the same folder at once.

For new tasks, a launch set opens several agents in one click, each in its own worktree. Agent Grid shows up to 16 at once with a status on every pane, Attention lists the ones waiting for you first, and when Claude Code or Codex hits a usage limit, Limit handoff moves the work to your other account with a brief you edit first. SwarmPane runs Claude Code, Codex, Antigravity CLI, Gemini CLI (with a Gemini API key), Cursor Agent, GitHub Copilot CLI, OpenCode, Grok Build, Kimi CLI, Aider, Droid, Devin and Hermes Agent.

A note on names

SwarmPane has a feature called Jev Conductor (beta). It routes a goal to one of your agents and runs your checks, and it has nothing to do with Conductor (conductor.build) or its move to Meta.

Try SwarmPane

SwarmPane is Starter at $17 a month, Pro at $29 or Ultra at $50, on Mac, Windows and Linux, and the app needs an active plan to open. Your Claude, ChatGPT, Cursor and other plans stay with their providers, which bill their own usage. Get SwarmPane. Starter and Pro start with a 5-day trial for $1.