Switching from Conductor
Conductor Cloud shuts down November 20. What to save, where your scripts and env vars go, and how to switch to Orchestrator.inc, free and open source.
Last updated November 10, 2026
What is happening to Conductor?
- November 4, 2026
Conductor announced it is joining Meta. New sign-ups and app downloads closed the same day.
- November 13, 2026
Cloud workspaces become read-only. Old chats can still be read and exported.
- November 20, 2026
Conductor Cloud shuts down and Cloud user data starts being deleted.
- Early 2027
The local Mac app, which keeps working for now, starts winding down.
From Conductor's announcement of November 4, 2026.
What to save before November 13
- 01
Export your data
Settings → Account → Export data in Conductor.
- 02
Push every branch, including work in progress
A pushed branch is all Orchestrator needs to pick the work up. Cloud workspaces can also be moved to your Mac with Transfer to local.
- 03
Keep your settings file
.conductor/settings.toml(plussettings.local.tomland~/.conductor/settings.toml), orconductor.jsonin older repositories. - 04
Note your agents and models
So you can pick the same ones per project.
Coming from Conductor Cloud?
Orchestrator Cloud runs your agents in cloud sandboxes, so work goes on after you close your laptop. It is its own product, not a copy of Conductor Cloud.
Agents keep running with your laptop closed
Each cloud session runs in its own sandbox on Freestyle or Coder, including your own Coder deployment. Idle sandboxes pause and resume when you come back.
Your agents, without your logins in the sandbox
Claude Code, Codex, Cursor and OpenCode run in the cloud. Agent sign-ins are held by Orchestrator's servers and models are reached through a proxy, so long-lived logins never sit in the sandbox.
An orchestrator in the cloud
It starts, messages and stops worker sessions and opens their pull requests, while you are away.
Work on a session together
Share session gives people Watch, Write to the agent or Start sessions access. Everyone sees who is there and shares one composer, with Request turn and Take over.
From issue to merge
Matching GitHub issues can start worker sessions. Automatically fix CI failures and Automatically fix review comments keep PRs moving, and merge requests wait for Approve and merge or Reject.
Your setup, in the cloud too
The same Setup and Cleanup scripts run in cloud sandboxes, and a project can span several repositories, or none.
Limits and prices are on the pricing page.
Let an agent do the setup
Here are two prompts for Claude Code, Codex or any coding agent. They are also in the Copy page menu at the top. Set up Orchestrator installs the desktop app for your system. Move my Conductor setup goes into a New task in your project, added with New project → Open a local folder. It reads .conductor/settings.toml, shows you every change and waits for your OK.
Show full prompt · paste into Claude Code, Codex or any coding agent
Install the Orchestrator.inc desktop app on this computer.
1. Check the operating system and CPU.
2. Install the latest release from https://github.com/OrchestratorInc/agent-orchestrator/releases/latest. Each file below downloads from https://github.com/OrchestratorInc/agent-orchestrator/releases/latest/download/<file>.
- macOS with Homebrew: brew install --cask agentwrapper/tap/agent-orchestrator
- macOS without Homebrew: Orchestrator-darwin-arm64.dmg (Apple silicon) or Orchestrator-darwin-x64.dmg (Intel). Open it and copy Agent Orchestrator.app to /Applications.
- Windows x64: agent-orchestrator-win32-x64.exe. Run the installer.
- Linux x64: agent-orchestrator-linux-x64.deb (Debian, Ubuntu), agent-orchestrator-linux-x64.rpm (Fedora, RHEL) or agent-orchestrator-linux-x64.AppImage. Install the package, or make the AppImage executable and run it.
Ask me before any step that needs my password.
3. Open the app.
4. Check which coding agents are installed and signed in here (for example Claude Code, Codex, Cursor or OpenCode), and whether the GitHub CLI (gh) is signed in. Tell me what is missing, and don't install anything else without asking.How to switch from Conductor in five steps
- 01
Install Orchestrator
Download the desktop app. No account is needed to run agents locally.
- 02
Add your repository
New project → Open a local folder, and pick the folder you opened in Conductor, not a fresh clone.
- 03
Bring your settings
Paste the prompt above into a New task, or copy each setting into Project Settings using the table below. Project settings docs.
- 04
Pick your agents
A worker agent, an orchestrator agent and, if you like, a reviewer. Orchestrator uses the agent CLIs already signed in on your computer. Per-role agents docs.
- 05
Hand off your first task
Continue one of your pushed branches, or describe a bigger job to the orchestrator and let it split the work. Quickstart.
Where each setting goes
| In settings.toml | In Orchestrator |
|---|---|
scripts.setup | Scripts → Setup (postCreate). Runs in the new worktree before the agent starts. |
scripts.archive | Scripts → Cleanup (preRemove). Runs before a worktree is removed. |
environment_variables | Environment. You can paste a .env file, or link one into every worktree with symlinks. |
prompts.general | Project rules (agentRules) |
scripts.run | A configuration in .ao/launch.json. One server runs per session. |
$CONDUCTOR_ROOT_PATH | $AO_SOURCE_TREE_PATH |
$CONDUCTOR_WORKSPACE_PATH | $AO_WORKTREE_PATH |
$CONDUCTOR_PORT | ${PORT} in .ao/launch.json, with "autoPort": true (one free port, not a range of ten). The server also gets it as the PORT environment variable. |
$CONDUCTOR_DEFAULT_BRANCH | No variable. Set Default branch in Project Settings. |
Same ideas, new names
| In Conductor | In Orchestrator |
|---|---|
| Project, added with Add repository | Project, added with New project → Open a local folder or Clone a repo |
| Workspace (one branch per task) | Session with its own worktree and branch, started with New task |
| Chat tab with a harness and model | Chat with the same agent, model and effort picker, or the agent's own Terminal UI. Local sessions can switch agents mid-conversation. |
| Scripts tab: Setup and Archive | Project Settings → Scripts: Setup and Cleanup |
| Run button and Preview URLs | A named server in .ao/launch.json, started with ao preview start <name> and shown in the session's Browser pane |
| Diff Viewer | Changes and Diff |
| Checks tab | The Board: Building, Validating, In review, Ready |
| Review | A reviewer agent on each PR |
| Create PR, Merge PR | Create PR, Merge |
| Archive workspace, restore from History | Archive session, Restore session |
| Conductor Cloud | Orchestrator Cloud, from $20/month. A different product with its own limits. |
Help
Ask in the Orchestrator Discord.
Moving a whole team? Book a setup call with the founder, and the Orchestrator team will set it up with you.
FAQ
Is Conductor shutting down?
Conductor announced on November 4, 2026 that it is joining Meta. Conductor Cloud becomes read-only on November 13 and shuts down on November 20, 2026. The local Mac app keeps working for now and starts winding down in early 2027.
What is a good open-source alternative to Conductor?
Orchestrator.inc is a free, Apache-2.0 desktop app that runs coding agents in parallel Git worktrees like Conductor, on macOS, Windows and Linux. It adds an orchestrator agent that splits the work and sends CI failures and review comments back to the right agent, and it supports 38 coding agents.
Can an agent move my Conductor setup for me?
Yes. The Set up Orchestrator prompt on this page installs the app, and the Move my Conductor setup prompt goes into a task in your project. That agent reads .conductor/settings.toml, shows you the ao project set-config command and waits for your OK, then sets up your scripts, environment and rules, and opens a PR that adds your run actions as .ao/launch.json.
Can I import my Conductor chat history?
No. Orchestrator has no Conductor importer, and the format of Conductor's exported data isn't documented. Push your branches and continue them in new sessions.
Is Orchestrator a Claude wrapper?
No. It runs 38 coding agents through the CLIs you already have installed and signed in, and usage is billed by your own provider account.
Does Orchestrator work for teams?
Yes. Locally, each person runs it on their own machine and the work meets in pull requests. On Orchestrator Cloud you can share a session by link, see who is in it and take turns prompting the same agent. SSO and team management are coming soon.
How much does Orchestrator cost?
The desktop app is free and open source (Apache-2.0), with unlimited local agents. Orchestrator Cloud is Starter at $20/month or Pro at $40/month, and Enterprise is priced on request. Reaching your computer from your phone away from home through the managed HTTPS tunnel needs Starter or above.