Skip to content
All guides

Migration

Conductor alternatives in 2026: Mac, Windows, Linux and cloud options compared

Conductor isn’t shutting down after all. What changed after the Meta deal, the Conductor alternatives compared for macOS, Windows and Linux, and how to move if you want to.

By Updated 12 min read

Banner reading “Conductor alternatives in 2026”, with an arrow from the Conductor app icon to the icons of the alternatives this guide compares: Concors, Orca, Traycer, Paseo, Pane, Nimbalyst, Parallel Code and boxes.dev.

Is Conductor shutting down?

No. Conductor made running several coding agents side by side feel normal, and many developers built their workflow around it. On November 4, 2026 the team announced it was joining Meta and winding Conductor down. Eight days later it changed course: its announcement now reads “Plans have changed! We’ll still be developing Conductor,” and its FAQ answers “Is Conductor shutting down?” with “Nope! Conductor will keep working as normal.”

  1. Nov 4Conductor announces it is joining Meta, with Conductor Cloud to go read-only on November 13 and shut down on November 20
  2. Nov 12Co-founder Charlie Holtz posts that development will continue at Meta: “Reports of our death have been greatly exaggerated (by us)”
  3. Nov 13Conductor 0.94.2: “Conductor isn’t shutting down. It’s back, and we’re building again.” The Cloud shutdown banner is removed and the shutdown dates are crossed out

So if you use Conductor and it works for you, you don’t have to move. People still compare alternatives for other reasons: Conductor runs only on macOS, its team is now part of Meta, and the two-week shutdown notice showed how quickly a hosted tool can change. The tools below are what people were moving to, and they’re still the options if you want Windows or Linux, open source, or a machine that stays on.

Conductor’s two ways to take your work with you still exist. Right-click a cloud workspace and choose Transfer to local to move it and its chats to your Mac, or go to Settings → Account → Export data to download everything.

This guide is about Conductor from conductor.build, the Mac app for running coding agents in parallel, not other products with the same name.

How do I keep my Conductor setup portable?

Some of what you set up in Conductor Cloud lives only in Conductor’s settings, not in your repository. Whether you stay or move, keep a copy so a change of plans can’t strand your work:

  • Commit and push every branch, including new files (git add -A). Work an agent committed in a cloud workspace but never pushed exists only there.
  • Copy the files Git doesn’t push. Gitignored files such as .env never reach your Git host, and Conductor keeps workspace notes and attachments in a gitignored .context folder inside each workspace.
  • Export your data from Settings → Account → Export data, and keep the file outside Conductor. To keep a workspace and its chats on your Mac, use Transfer to local.
  • Copy your Cloud Computer setup. The Install software script and each repository’s setup script are edited in your organization’s settings in Conductor Cloud, not read from your repo, so pushing your branches doesn’t save them. Paste each one into a file.
  • List your environment variables and secrets by name. Conductor hides values after you save them, so get each value from its source, such as your password manager.
  • Write down your routines: the prompt, the repository and what triggers each one.
  • List the work in flight. One line per workspace: what the agent was doing and what is left.
  • Try any new tool on your real repo, side by side with Conductor, before you rely on it.

What are the best Conductor alternatives?

The tools people are moving to differ most in one thing: where your agents run. Some are desktop apps that run agents on the computer in front of you. Some connect to servers you run. A few run agents on machines in the cloud, which is what Conductor Cloud did.

ToolDesktopWhere agents runPhoneSource
ConcorsmacOS (Apple Silicon), Windows, LinuxYour computer, or a Concors Cloud machine that stays on, at a flat monthly priceiOS; Android coming soonOpen source (MIT)
OrcamacOS, Windows, LinuxYour computer, remote servers, SSH hosts and cloud VMsiOS and Android companionOpen source (MIT)
TraycermacOS, Windows, LinuxYour computer or other machines you own; cloud sandboxes as a paid add-oniOS and AndroidOpen source (MIT)
PaseomacOS, Windows, Linux, plus webAny machine running its daemoniOS and AndroidOpen source (Apache-2.0)
PanemacOS, Windows (x64, ARM64), LinuxYour computer (including WSL), or machines you own via Remote PaneIn the browser via Remote Pane; apps coming soonOpen source (AGPL-3.0)
NimbalystmacOS, Windows, LinuxYour computeriOS appOpen source (MIT)
Parallel CodemacOS, LinuxYour computerProgress via QR codeOpen source (MIT)
boxes.devWeb, CLICloud devboxes that sleep when idle, billed by compute timeiOS and Android—
ConductormacOSYour Mac, or Conductor Cloud sandboxesiOS appClosed source

Checked against each product’s own website on November 8, 2026. The Conductor row was updated on November 14, after Conductor reversed its shutdown. Features change quickly; follow the links in Sources.

Which Conductor alternative should you pick?

  • You want a free app on your own computer, on any OS: Orca, Traycer, Pane or Nimbalyst. All four run on macOS, Windows and Linux and are open source.
  • You already run your own servers: Paseo (install its daemon anywhere) or Orca (SSH hosts and cloud VMs).
  • You want cloud machines that sleep when idle, and pay for the time they’re awake: boxes.dev.
  • You want one machine that stays on, with your agents, terminals and dev servers still running tomorrow, at a flat monthly price: Concors.
  • You’re on a Mac and happy with Conductor: stay. It isn’t shutting down, and it has cloud sandboxes and an iOS app.
  • You only use one agent: Claude Code can start each session in its own worktree with claude --worktree, and the Codex app can run a chat in its own worktree.

What changes when you move from Conductor Cloud to Concors?

Conductor Cloud gave each workspace its own sandbox, built from one shared Cloud Computer per organization. Concors gives you a machine you set up once and that keeps running. Most things have a counterpart; a few work differently, and some have no equivalent yet:

In Conductor CloudIn ConcorsWhat to do
One Cloud Computer per organizationA Concors Cloud machine owned by your organization, billed monthlyCreate one machine for the repos you worked on together
A sandbox per workspace (one repo and branch)A workspace is a folder on the machine; agents in it share its filesGive each branch its own folder with git worktree
Sandbox: 8 vCPUs, 16 GB RAM2 vCPU / 4 GB up to 8 vCPU / 24 GB, with 40–200 GB diskPick the size closest to what your builds used
Amazon Linux 2023; install scripts used dnfUbuntu 24.04, with optional Node.js, Python and uv, Go, Rust and DockerChange dnf install lines to apt packages and run them in a terminal
Repo setup scripts ran in each new workspaceNot described in Concors’s docsCommit the script to your repo and run it after you clone
Organization variables and secretsNot described in Concors’s docsPut values in the repo’s gitignored .env on the machine
Conductor managed Git and GitHub CLI sign-inGit uses the machine’s own credentialsAdd an SSH key, then run gh auth login on the machine
Forwarded portsPreviews finds dev servers and gives each port an address only your account can openStart your dev server on any port and open it from Previews
Workspaces slept after 20 minutes idle and stopped after 23 hours 50 minutesThe machine keeps running, at a flat monthly price with no usage componentLeave long jobs running
Claude Code, Codex, Cursor, OpenCodeClaude Code, Codex and OpenCode, as their real CLIs with your own accountsTest any other agent before you rely on it
Routines on a schedule, GitHub event or webhookSchedules run a saved prompt every 15 minutes or more, daily or weeklyRecreate scheduled routines; event triggers aren’t described
Multiplayer: shared chats, Follow, Reassign toNot offeredIf your team depends on it, check team features before you move
iOS appAvailable on the App StoreAdd your machine in the desktop app, then connect from iOS
Chats stored on Conductor’s serversNo importerPaste the context an agent needs into its first message

What replaces Conductor’s environment variables?

If your scripts read Conductor’s variables, swap in plain shell that works on any machine:

Conductor variableUse instead
CONDUCTOR_WORKSPACE_PATHgit rev-parse --show-toplevel
CONDUCTOR_ROOT_PATH (main checkout)dirname "$(git rev-parse --path-format=absolute --git-common-dir)"
CONDUCTOR_WORKSPACE_NAMEbasename "$PWD" or git branch --show-current
CONDUCTOR_DEFAULT_BRANCHgit symbolic-ref --short refs/remotes/origin/HEAD
CONDUCTOR_PORTA fixed port per checkout, for example PORT=3001 in its .env
CONDUCTOR_IS_LOCALRemove the branch; keep the steps for your new machine
CONDUCTOR_API_URL, CONDUCTOR_API_TOKENNo replacement; remove calls to the Conductor API

How do I move from Conductor to Concors?

Concors is a desktop app for macOS, Windows and Linux. Claude Code, Codex and OpenCode run as their real CLIs with your own accounts, next to your terminals and dev servers. There is no Conductor importer yet, so the move is manual: a few minutes per repo.

  1. Install the app

    Download Concors. It opens straight into a workspace on your own computer, with no account, so you can try it before deciding anything.

  2. Create a machine that stays on

    In Settings → Machines → New machine, choose a region (United States, Europe or Canada), a size from 2 vCPU / 4 GB up to 8 vCPU / 24 GB, and the tools to install: Node.js, Python and uv, Go, Rust, Docker. This step asks you to sign in. Machines are billed monthly, and the price is shown before you confirm.

  3. Bring your repos

    Connect GitHub and clone the branches you pushed, or clone them from a terminal on the machine.

  4. Sign in to your agents

    Use the same Claude and ChatGPT accounts you used with Conductor. Subscriptions and usage stay with each provider.

  5. Restart the work

    Run your setup steps in a terminal, start the dev server and open it from Previews in the sidebar. Then hand each agent the line you wrote about its unfinished work.

Two terminals side by side in one Concors tab: the Vite dev server on the left and Vitest in watch mode on the right, with all 5 tests passing.
A dev server and a test watcher running side by side in one Concors tab.

Close the app when you are done for the day. The agents, terminals and dev server keep running on the machine, and everything is where you left it when you come back.

How do I move a local Conductor workspace to Concors on my Mac?

If you used Conductor on your Mac, or ran Transfer to local, your work is in ordinary Git worktrees, usually under ~/conductor/workspaces. Concors can open them where they are; nothing is copied. Concors runs on Apple Silicon Macs (M1 or later); Intel Macs aren’t supported.

  1. Find your workspaces

    From your main checkout, run git worktree list. Each path under ~/conductor/workspaces/ is a Conductor workspace.

  2. Open each one in Concors

    Click + next to Workspaces, choose Open folder… and pick the workspace folder. It keeps its branch and uncommitted changes.

  3. Pick up the conversation

    Claude Code ties a conversation to the folder it ran in, so from the same folder you can usually resume it with claude --resume in a terminal tab.

  4. Run your setup and dev server

    Your commands are in .conductor/settings.toml (or the older conductor.json). Run them in a terminal tab, and replace $CONDUCTOR_PORT with a fixed port.

Quit Conductor rather than archiving workspaces you’ve opened in Concors, and remove each one with git worktree remove when you’re done. On your own computer, agents stop when your Mac sleeps; for work that keeps going with the lid closed, use a Concors Cloud machine.

What doesn’t Concors do yet?

If you need these today, Orca and Traycer create a worktree per agent and have phone apps. New Concors versions ship several times a week; the changelog lists each one.

Questions

Written by

Tong Pow

Works on Concors at Hologram

XGitHub

Sources

More guides

Let your agents
keep working.

Claude Code, Codex and OpenCode on a machine that stays on. Free on your own computer, no account needed.

Desktop app for macOS (Apple Silicon), Windows (x64) and