# Switching from another tool

Coming from Conductor, Paradev (formerly Superset), Claude Squad, or your own `git worktree` setup? You don't have to start over. Pane can take over worktrees that already exist, read your old project scripts, and pick up an agent's conversation where you left off.

> **Note:** Conductor Cloud went read-only on November 13, 2026, and its data is deleted from November 20, 2026. Right-click each remaining Cloud workspace in Conductor and choose **Transfer to local** or export an archive ([Export your Conductor Cloud workspaces](/guides/migrate-from-conductor-cloud)), then bring the sessions in below.

## Bring your sessions in

Pane finds sessions from Claude Code, Codex, Conductor, Paradev, Herdr, Emdash, Orca and T3 Code on your computer, opens each checkout in place as a [pane](/docs/panes-and-worktrees), and resumes each conversation by the agent's own session ID. It doesn't delete anything.

- **On a new install**, the first screen offers to bring in sessions used in the last 7 days. Click **Yes**, and Pane groups them into [Sessions](/docs/sessions) and opens a Start here page listing what came over and what was left out.
- **Any time later**, go to **Settings → AI & Agents → Bring sessions into Pane** and click **Find sessions**. It lists sessions from the last 30 days, with the last 7 days preselected.
- **In [Pane Chat](/docs/pane-chat)**, say "migrate to Pane". It also finds Cursor and OpenCode sessions, and forks a session that's still running elsewhere onto a new branch instead of skipping it.

A session still running in its old tool can't be adopted from Settings. Quit it there and press **Check again**, or use "migrate to Pane".

The rest of this page is the manual route, one worktree at a time.

## 1. Add your repo

Add the main repository to Pane first. Click **+** in the sidebar, or run:

```bash
runpane repos add --path /path/to/my-app --yes --json
```

## 2. Keep your project scripts

If your repo has a `conductor.json`, Pane reads it. Its setup, run and archive scripts work in Pane without changes. Pane checks for config in this order: `pane.json`, then `conductor.json`, then `.gitpod.yml`, then `.devcontainer/devcontainer.json`. The first one that defines at least one script wins. See [Configuration](/docs/configuration).

## 3. Adopt your existing worktrees

[`runpane panes adopt`](/docs/runpane-cli) turns a worktree you already have into a pane. The worktree has to belong to the repo you added in step 1. Pane refuses anything else.

```bash
runpane panes adopt \
  --repo active \
  --path /absolute/path/to/existing-worktree \
  --name existing-work \
  --agent codex \
  --yes --json
```

1. Run it with `--dry-run` first. Pane checks the path without changing anything.
2. Add `--folder <name>` to put the pane in a sidebar folder.

The new pane shows up in the sidebar with an **External** label.

### Pick up the conversation

Pass the agent's session ID with `--resume <id>`. Pane types the agent's resume command into the terminal and waits for you to press Enter. Add `--launch` to run it right away.

> **Warning:** Don't drive the same conversation from two apps at once. Both write to the same transcript.

## What "External" means

Pane didn't create an adopted worktree, so Pane doesn't own it:

- Pane never deletes, rebuilds or re-copies files into it.
- Archiving the pane only removes it from Pane. The folder stays.
- Want Pane to remove it anyway? Run `runpane panes archive --pane <id> --remove-worktree --yes`. Pane runs the same safety check as always: uncommitted, untracked or unpushed work blocks it unless you add `--force`. Your local branch is kept.

## Moving many worktrees

[Bring your sessions in](#bring-your-sessions-in) handles most tools in one go. For a tool it doesn't know, list your worktrees with `git worktree list` and adopt each one. Or ask a [Session](/docs/sessions) to do it for you:

> Adopt every worktree of this repo that isn't in Pane yet, and resume each one with Claude Code.

## Related

- [Panes & Worktrees](/docs/panes-and-worktrees)
- [runpane CLI](/docs/runpane-cli)
- [Configuration](/docs/configuration)
