Get Started

Migrate from Conductor Cloud

Move your Conductor Cloud workspaces to Orca on your Mac or in the cloud

If you choose to move from Conductor Cloud, this guide helps you continue on your Mac or in a Orca cloud workspace.

Save your work

Work that exists only in a Conductor Cloud workspace is not on your machine. Save the branches and files you want to move before switching.

For the local Conductor app, see Migrate from Conductor.

What Maps to What

Conductor CloudOrca
Cloud workspaceCloud workspace
Cloud setup: repositories, variables, secretsEnvironment with variables
Setup script and actions.orca/config.json (lifecycle scripts)
RoutinesAutomations with Cloud as the device
iOS appiPhone and iPad app
Cloud organizationOrca organization. Environments are visible to the whole organization by default

1. Save Your Work in Conductor

Save the work you want to move before switching.

  1. Push every branch. In each Conductor Cloud workspace, commit all changes, including new files (git add -A), and push the branch. A pushed branch is safe on GitHub whatever you choose next. A push does not include Git-ignored files, such as .env files or local data. Copy any you need before leaving the workspace.
  2. Export your data. In Conductor, go to Settings → Account → Export data. This keeps a copy of your chats. Orca cannot import Conductor chats, so this export is your record of them.

Then pick where to continue: on your Mac, or in a Orca cloud workspace.

2a. Continue on Your Mac

  1. In Conductor, right-click the cloud workspace and choose Transfer to local. Conductor moves the workspace and its chats to your Mac.
  2. Follow Migrate from Conductor to import the workspace into Orca and convert your scripts.

Conductor can attach a cloud workspace on your Mac to its own copy of the repository under ~/conductor/, not to your clone. Then the workspace does not appear in your project's import list. To check, run this in the workspace folder:

git rev-parse --path-format=absolute --git-common-dir

If the path is under ~/conductor/, commit and push the branch from that folder. Then create a workspace from the Existing branch in your own clone.

If you only pushed the branch, add the repository in Orca and create a workspace from the Existing branch instead. See Workspaces.

2b. Continue in a Orca Cloud Workspace

Orca cloud workspaces keep agents working when your laptop is closed, and you can open them from desktop, iPhone, or iPad. They are available on paid plans, with shared included usage and metered extras. The GitHub repository must be shared with the Orca GitHub App. See Requirements.

Add your setup scripts

Cloud workspaces run the setup scripts in .orca/config.json from the repository. Convert your Conductor setup script as described in Convert Your Scripts, then commit and push the file to every branch you will use as a base branch. A cloud workspace started from a branch without it does not run your setup.

CONDUCTOR_PORT is not set in Conductor Cloud, so cloud scripts usually do not need a port change.

Create an environment

  1. Open Settings → Environments and click New environment.
  2. Add the repositories your Conductor Cloud workspaces used. The first one is the primary.
  3. Click the environment and add the variables and secrets your Conductor Cloud setup used.

Do not add agent API keys or GitHub tokens. Cloud workspaces ignore them: agents use your sign-in from Settings → Agents, and GitHub access comes from your connected GitHub account. See Credentials.

Not sure what the project needs? Click Set up with an agent in Settings → Environments. Claude installs what the project needs and writes its .orca/config.json.

Continue each branch

  1. Press ⌘N and pick Cloud in the device picker.
  2. Pick the project and the environment.
  3. Choose the branch you pushed from Conductor as the base branch. Orca creates a new working branch from it, so an open pull request for the Conductor branch does not get the new commits. Open a new pull request from the new branch, or merge it into the old one.
  4. Tell the agent where to pick up, for example "Continue the work on this branch. Read the last commits and the open PR first."

From the CLI:

orca workspaces create --base-branch <pushed-branch> --agent claude \
  --prompt "Continue the work on this branch"

If more than one environment has repositories, also pass --environment <id>. Run the command without it to see each environment's ID.

When one workspace is fully set up, right-click it and choose Save as environment. New workspaces then start from that snapshot instead of running setup each time. See Save a set-up workspace.

Move your routines

Recreate each Conductor routine as a Orca automation. Pick Cloud as the device to run each session in a new cloud workspace, and pick the machine size. Automations can run on a schedule or when something happens in GitHub, Slack, Linear, Sentry, and other tools.

3. Check Your Usage

Orca meters cloud usage in GB-hours: machine memory multiplied by run time. A stopped or sleeping workspace uses none, and a workspace stops by itself after about an hour of no activity. Settings → Billing shows what you have used. See Usage and Billing.

Get Help

Stuck on a step? Ask in the community or see Troubleshooting.

On this page