Move from Conductor

Push every branch

Push each branch you want to keep, including unfinished work. In the workspace terminal:

git add -A && git commit -m "WIP: move from Conductor" && git push -u origin HEAD

Git does not push ignored files such as .env. Copy those separately.

Transfer the workspaces you want to continue

Right-click each Cloud workspace and choose Transfer to local. Conductor moves the workspace and its chats to your Mac.

Export your account

Choose Settings → Account → Export data and keep the archive.

Write down your Cloud settings

Copy your Cloud setup script, environment variables, secrets, run actions, and routines somewhere safe. You set them up again in Orchestrator.

Add the repository

Choose New project → Open a local folder and pick the repository Conductor uses as the root, not a folder under ~/conductor/workspaces. Orchestrator creates its own worktree and branch for each session, so your Conductor workspaces stay where they are.

Copy the Conductor settings

Conductor keeps a repository's settings in .conductor/settings.toml, with personal overrides in .conductor/settings.local.toml, or in conductor.json in older repositories. Open Project settings → Scripts and copy each setting:

A Setup step runs in the new worktree, so a copy step looks like this:

cp "$AO_SOURCE_TREE_PATH/.env" .env

Rename the Conductor variables

Setup and Cleanup steps get Orchestrator's names instead of Conductor's:

Continue the work

Start a session on each branch you want to continue. Your Conductor chats stay readable in the Conductor app.

Create a Cloud project

Follow Cloud sessions to create a project from the same GitHub repository. Each session gets its own remote workspace, as in Conductor Cloud.

Set up your scripts

Open the Cloud project's Project settings and add the Cloud settings you wrote down:

• Scripts → Setup: your Cloud Computer install script first, then the repository's setup script.
• Scripts → Cleanup: the archive script.
• Environment: your Cloud environment variables and secrets.
• Cues: each run action.
• Instructions: the general prompt.

Rename the Conductor variables using the table above. Conductor Cloud ran Amazon Linux; check package commands such as dnf install in the new workspace.

Continue the work

Start a session on each branch you pushed. For a workspace you transferred to your Mac, add its repository as in Move a repository.