Docs / Migrate

Migrate from Conductor Cloud

Move work from Conductor Cloud to Pangea Cloud computers or your own machines, and keep going with your team.

Conductor Cloud runs coding agents in cloud workspaces. If your team wants to run that work on Pangea, you can move it to Pangea Cloud computers or to your own machines. Work that lives only in a cloud workspace is not on your Mac yet, so save it first. Then pick it up in Pangea.

How the two fit together

1. Save your work in Conductor Cloud

Do this for every cloud workspace you want to keep.

1. Push every branch. Ask the workspace's agent, or use a terminal in the workspace, to commit and push the branch. Include work in progress:

bash git status --short # Review the files, then stage only the paths you want to keep. git add <reviewed-paths> git commit -m "WIP: move from Conductor Cloud" git push -u origin HEAD

If there is nothing to commit, just push the branch. Check the staged files for secrets before you commit. A push only includes committed files. Copy anything git ignores that you still need, such as .env files or local data, to a safe place.

2. Or transfer the workspace to your Mac. In Conductor, right-click the workspace and choose Transfer to local. It becomes a local workspace. You can then bring it into Pangea with Migrate from Conductor.

3. Export your data. In Conductor, open Settings → Account → Export data and keep the download. Pangea can't import Conductor Cloud chats directly, so this export is your record of them.

4. Write down your cloud setup. Note the repositories, setup scripts, environment variables and secrets your organization's Cloud Computer uses, and any routines. You will set them up again in Pangea. Copy secret values from where you first stored them, not from chat logs.

2. Set up your Pangea team

1. Sign up and install the app. Create your account at app.pangea.build and install the Mac app. See the Quickstart. Pangea creates a team for you, and you are its admin.

2. Connect GitHub. Open Connectors, choose GitHub and select Install GitHub App. Install it on your GitHub organization and pick the repositories you used in Conductor Cloud. See GitHub.

3. Add a computer. Open team Settings → Computers and choose Add computer. Only admins can do this. Pick where agents run:

   • Pangea cloud computer. A Linux computer in the cloud that Pangea runs for your team, with Claude Code and Codex on it. Give it a name, a size, and choose Who can use it: Admins only, Everyone or Specific people. Agents keep working when everyone's laptop is closed.
   • Your own computer. A laptop or server you run. Pangea connects to it over your own SSH, or you run a one-time command on it. See the CLI.

Then sign in to Claude Code or Codex on that computer with your own account. Model usage stays on your own subscription. See Runtimes and computers.

4. Prepare the computer. Start an agent on the new computer. Ask it to set up your repositories, the way your Conductor Cloud setup scripts did:

"Clone acme/web and acme/api into ~/code, install their dependencies, and run their tests. Tell me what's missing."

Put the steps every new task needs in CLAUDE.md or AGENTS.md in the repository, or save them as a team skill. Then every agent follows them. Create .env files and other secrets on the computer yourself. Don't paste them into a chat.

5. Invite your teammates. Open team Settings → Members, invite people by email and pick a role. See Teams for what each role can do.

3. Continue each branch

For each branch you pushed in step 1, start an agent on the cloud computer and tell it where to pick up:

"Check out branch fix-login-redirect of acme/web in a new worktree. Read the diff against main and continue. The login redirect still drops the next parameter."

If you exported a chat, attach the useful part to your first message. In the composer, choose + → Attach. The agent then has the history.

If you transferred a workspace to your Mac instead, you can keep working on it there. Later, move the conversation to the cloud computer from its runtime menu, then confirm Move.

4. Work as a team

• Bring someone in. @mention a teammate in a conversation and choose Invite. Everyone in the conversation sees the same tool calls and can steer the agent.
• Hand work off. Invite the teammate who takes over. The conversation and its history stay where they are.
• Share a computer. A cloud computer's Who can use it setting decides who can run agents on it. A teammate can also share their own computer. See Runtimes and computers.
• Share what agents learn. Memories and team skills belong to the team. The next agent starts with what the last one learned.

5. Recreate routines as triggers

A Conductor routine becomes a trigger. Open team Settings → Triggers. A trigger runs an agent on a schedule or from a webhook, with a message that starts each run. For example, a nightly dependency check can run every night at 02:00 UTC with the message "Update dependencies in acme/web, run the tests, and open a pull request if they pass."

FAQ

Can Pangea import my Conductor Cloud chats?

Not directly. Keep the export from Settings → Account → Export data in Conductor. If you transfer a workspace to your Mac, you may be able to continue its Claude Code session. In the composer, choose + → Continue a Claude Code session. See Migrate from Conductor.

Do I have to use Pangea Cloud computers?

No. Agents can also run on a computer you manage, or on your Mac with the desktop app. You can mix them in one team.

Who pays for the models?

You do, through the account each runtime signs in with, such as your Claude or ChatGPT subscription. Pangea plans are separate. See Plans and billing.

Where do my secrets go?

Cloud accounts and tools such as AWS, GCP and GitHub connect under Connectors. Agents use only the connections they are allowed to use. App secrets, such as .env files, stay on the computer where you put them.

Can I keep using Conductor while I try Pangea?

Yes. Your code stays in git, so both can work on the same repositories. Avoid having two agents edit the same branch at the same time.