# Switching from Conductor

URL: https://orchestrator.inc/migrate/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.

## Timeline

- 2026-11-04: Conductor announced it is joining Meta. New sign-ups and app downloads closed the same day.
- 2026-11-13: Cloud workspaces become read-only. Old chats can still be read and exported.
- 2026-11-20: 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.

## 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.

## Steps

1. **Install Orchestrator**: Download the free desktop app for macOS, Windows or Linux. No account is needed to run agents locally.
2. **Add your repository**: Choose New project, then Open a local folder and pick the folder you used with Conductor.
3. **Bring your settings**: Paste the migration prompt into a new task, or copy each setting into Project Settings using the table.
4. **Pick your agents**: Choose a worker agent, an orchestrator agent and, if you like, a reviewer.
5. **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.

## Prompt: Set up Orchestrator

Paste into any coding agent on the computer to install the desktop app.

```text
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.
```

## Prompt: Move my Conductor setup

Paste into a new task in the Orchestrator project for the repository you used with Conductor.

```text
I'm moving this repository from Conductor to Orchestrator. Please migrate my Conductor setup for this project.

1. Find the project folder with `ao project get $AO_PROJECT_ID`. Read .conductor/settings.toml and .conductor/settings.local.toml there, and ~/.conductor/settings.toml. If none of them exist, read conductor.json instead.

2. Map the settings to `ao project set-config $AO_PROJECT_ID` flags:
   - scripts.setup -> --post-create (one flag per step)
   - scripts.archive -> --pre-remove
   - environment_variables -> --env KEY=VALUE (one flag per variable)
   - prompts.general -> --agent-rules
   In every script, replace $CONDUCTOR_ROOT_PATH with $AO_SOURCE_TREE_PATH and $CONDUCTOR_WORKSPACE_PATH with $AO_WORKTREE_PATH.

3. Before running anything, show me the full set-config command, listing environment variable names but not their values, and wait for my OK.

4. For each run action in scripts.run, add a configuration to .ao/launch.json ({"version": 1, "configurations": [...]}, one per action: the action's key -> name, command -> runtimeExecutable, args -> runtimeArgs, options.cwd -> cwd, and "autoPort": true). runtimeExecutable is run as one program, not through a shell, so if command is a shell line such as "npm run dev", use "runtimeExecutable": "sh" with "runtimeArgs": ["-c", "<the command and its args>"]. Replace $CONDUCTOR_PORT with ${PORT}: Orchestrator fills in ${PORT} in runtimeArgs, url and env, and also sets PORT in the environment. Commit it on this branch and open a PR. Tell me to start each one with ao preview start <name>.

5. Tell me what you could not map, such as run_mode, other prompts or other CONDUCTOR_ variables.

6. List the remote branches that are not merged yet, so I can choose which ones to continue.
```

## Help

Ask in the Orchestrator Discord (https://discord.com/invite/UZv7JjxbwG). Moving a whole team? Book a setup call with the founder (https://cal.com/agentwrapper/ao-design-partner), 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.