Docs / Migrate

Migrate from Conductor

Bring your Conductor repositories, worktrees, scripts and Claude Code or Codex sessions into Pangea so your team can work on them together.

Conductor is a good way to run coding agents on your own Mac. When your team wants to work on the same agents together, you can bring that work into Pangea. Your code stays in git, so there is nothing to export. You point a Pangea agent at the same folders and keep going.

You can also keep using Conductor while you try Pangea. Both work on ordinary git checkouts.

How the two fit together

Conductor gives each task its own git worktree on your Mac. Pangea runs the coding agent you already use, such as Claude Code or Codex, in a conversation your team can join. The agent can run on your Mac or on a cloud computer.

1. Sign up and add a local runtime

1. Create your account. Sign up at app.pangea.build and install the Mac app. See the Quickstart. Pangea creates a team for you the first time.
2. Use the Claude Code or Codex already on your Mac. Open Settings → This computer → Local runtime. Pangea finds the Claude Code and Codex CLIs on your Mac. Each one signs in with your own account, so inference keeps running on your existing subscription. See Plans and billing.
3. Start an agent. Choose New agent in the sidebar, or press ⌘N. Pick the local runtime in the composer.

A local runtime works only while Pangea is open. To keep agents working after you close the laptop, an administrator can add a cloud computer under Runtimes in team settings. See Runtimes and computers.

2. Keep working in your existing worktrees

Conductor creates each workspace as a git worktree, usually under ~/conductor/workspaces/<repo>/<workspace>. A worktree is an ordinary git checkout. List them from the original repository:

git worktree list

A local runtime runs on your Mac as you, so an agent can work in any of these folders. Start one agent per workspace and name the folder in your first message:

"Work in ~/conductor/workspaces/web/warsaw. It is on branch fix-login-redirect. Read the diff against main and continue the task."

The local runtime also has its own Workspace folder. You can see it under Settings → This computer → Local runtime. Agents start there when you don't name a folder.

For a new task, ask the agent to create the worktree it needs. For example: "Create a worktree for a new branch add-billing-export off origin/main and work there." The agent uses git worktree the same way you would.

3. Convert your scripts

Conductor reads setup, run and archive scripts from .conductor/settings.toml or the older conductor.json. Pangea has no such file. It does not run scripts on its own when a conversation starts. Move the commands into files the repo already owns, and tell the agent when to run them.

A typical conductor.json:

{
  "scripts": {
    "setup": "pnpm install && cp \"$CONDUCTOR_ROOT_PATH/.env\" .env",
    "run": "pnpm dev --port $CONDUCTOR_PORT",
    "archive": "./scripts/archive.sh"
  },
  "runScriptMode": "nonconcurrent"
}

becomes a script in the repo, scripts/setup.sh:

#!/usr/bin/env bash
set -euo pipefail
pnpm install
# The main checkout is the first entry in `git worktree list`.
root="$(git worktree list --porcelain | sed -n 's/^worktree //p' | head -n 1)"
[ -f .env ] || cp "$root/.env" .env

and a note the agent reads. Claude Code reads CLAUDE.md and Codex reads AGENTS.md from the repository on its own:

## Working in a new worktree
- Run `scripts/setup.sh` once before anything else.
- Start the dev server with `pnpm dev --port <port>`. Pick a free port and
  tell me which one you used.
- Before deleting a worktree, run `scripts/archive.sh`.

What changes:

• CONDUCTOR_ROOT_PATH: use the first entry of git worktree list, as above, or an absolute path.
• CONDUCTOR_WORKSPACE_PATH: use the current directory, or git rev-parse --show-toplevel.
• CONDUCTOR_WORKSPACE_NAME: use the folder name, basename "$PWD", or the branch name, git branch --show-current.
• CONDUCTOR_PORT: Pangea does not assign ports. Pass a port yourself, or let the dev server pick a free one.
• Run button and run mode: there is no Run button. Ask the agent to start the server. To avoid two servers on one port, say so in CLAUDE.md.
• Archive script: it runs only when you or the agent run it.

If the same steps apply to many repositories, save them once as a team skill. Then every agent on the team follows them. You can also add standing guidance as instructions.

Let an agent convert them

Paste this into a Pangea agent that works in the repository:

"This repo has Conductor config in conductor.json or .conductor/settings.toml. Move the setup, run and archive scripts into scripts/. Replace every CONDUCTOR_* variable with git or plain shell equivalents. Add a short section to CLAUDE.md (and AGENTS.md if it exists) that tells an agent when to run each script. Leave the Conductor files in place and show me the diff before committing."

4. Bring over your agent sessions

Claude Code and Codex keep their own session history on your Mac. Claude Code uses ~/.claude/projects. Codex uses ~/.codex/sessions and ~/.codex/archived_sessions. Pangea can continue those sessions:

1. Start a new conversation. Choose New agent and select the runtime you want to continue on.
2. Open the session list. In the composer, choose + → Continue a Claude Code session or Continue a Codex session. Pick the session.
3. Keep going. The session's turns become the new conversation's transcript. The agent treats them as its own earlier context when you send your first message.

The imported conversation is a normal Pangea conversation. You can later move it to a cloud computer or invite a teammate into it.

5. Day to day in Pangea

What's different

• No automatic worktrees. Conductor creates a branch and a worktree for every workspace, and gives you a place to review and merge them. Pangea does not have one-click parallel agents in separate worktrees with review and merge yet. In Pangea, the agent creates a worktree when you ask, using git.
• No setup or run script hooks. Scripts run when you or the agent run them, guided by CLAUDE.md, AGENTS.md or a team skill.
• No built-in port allocation. Choose ports yourself.
• More places to run. The same conversation can move between your Mac and a cloud computer.
• Built for teams. Teammates can join a conversation and steer the same agent. Team skills can be reused across the team. Conversation access, computer access and personal credentials have separate controls. Being on a team does not make your private work public.

FAQ

Do I need to re-clone my repositories?

No. A local runtime works in the folders already on your Mac, including Conductor's worktrees. Clone again only when you move work to another computer, such as a cloud computer.

Does Pangea charge for model usage?

No. Each runtime signs in with your own Claude, ChatGPT or other provider account, and inference runs on that subscription. Pangea plans are separate. See Plans and billing.

Can I keep using Conductor while I try Pangea?

Yes. Both work on ordinary git worktrees. Avoid having two agents edit the same worktree at the same time.

Will Pangea read my .conductor/settings.toml?

No. Pangea has no per-repo config file. Convert the scripts as described in step 3.

Which agents can I use?

On your Mac, the local runtime supports Claude Code and Codex. Cloud computers support more runtimes. See Runtimes and computers.