> ## Documentation Index
> Fetch the complete documentation index at: https://wonder.design/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Move from Conductor

> Copy your Conductor workspaces into Wonder. The copy steps only read Conductor's folders.

Copy your Conductor branches and unfinished work into Wonder. The copy steps only read Conductor's folders, so you can check everything before switching.

**Before you start** · Desktop app · Free plan

Wonder is an independent product from Aquila Labs, Inc. It isn't affiliated with, sponsored by or endorsed by Conductor or Meta. Conductor, Claude Code, Codex, Cursor and OpenCode are names that belong to their owners. We use them only to say which apps this guide works with.

## What comes across

| | What happens |
| - | - |
| **Branches and commits** | Copied, including commits you haven't pushed |
| **Uncommitted changes** | Copied. Staged changes arrive unstaged |
| **`.env` and `.context`** | Copied. Other gitignored files are yours to copy |
| **Setup, run and archive scripts** | Run unedited once you accept them |
| **`CLAUDE.md`, `AGENTS.md`, skills, MCP** | Used as they are |
| **Claude Code memory for the repository** | Shows up in the clone, from `~/conductor/repos/REPO`. Chats in both apps share those notes, and they [stay in Wonder](#when-you’ve-finished-moving) after you delete `~/conductor` |
| **Recent Claude Code chats** | Continue them one at a time with `/resume`, while the workspace and its transcripts are still on your computer |
| **Codex chats** | Stay in Conductor. Start a new chat on the same branch, and ask it to read the branch's changes |
| **Scripts in `~/.conductor/settings.toml`, environment variables and API keys set in Conductor** | Stay behind. Add them again |
| **Cursor and OpenCode chats, pins, sections, diff comments, archived workspaces and other preferences** | Stay behind |

## Conductor's dates

[Conductor's announcement](https://www.conductor.build/announcement) says it's joining Meta, and gives these dates. We checked them on November 6, 2026. Its page is the one to trust.

* **November 13:** Conductor Cloud goes read-only. Conductor says you can still read old chats and export data.
* **November 20:** Conductor Cloud shuts down, and Conductor begins deleting Cloud user data.
* **Early 2027:** Local Conductor starts winding down. Conductor says it works as normal until then.

**Using Conductor Cloud?** Conductor says to right-click a cloud workspace and choose **Transfer to local**, so do it before November 13 if you can. Conductor asks you to export your data with **Settings → Account → Export data** before November 20.

## Before you start

1. Finish any chat running in your workspaces. Continuing a chat in two apps splits its history.
2. This guide needs a repository with a remote, such as GitHub.
3. If your employer provides your Conductor or your repository, check their rules before you copy anything.

## Let your agent move it

The agent moves all your recent workspaces once you approve one plan. A workspace is recent if it has uncommitted files or commits not on the remote, or if its last commit or newest chat is under 30 days old. The plan names what stays behind. To move an older one, ask the agent or [copy it by hand](https://wonder.design/docs/migrate-from-conductor-by-hand).

1. Update Wonder to version 0.2.220 or later.
2. In the sidebar, click **Create quick chat**, or the **+** next to **Quick chats** if you already have some. Set the chat to **Auto** so it asks only for the plan and the card; in **Ask**, you'll approve its commands as it goes. Send "Move my work from Conductor to Wonder."
3. Read the plan and reply OK. To move more or fewer workspaces, tell the agent. Then click **Allow** on the **Add these to Wonder?** card, which lists each repository and branch. Wonder opens each branch as a worktree on your workspace's commit, and your chat stays where it is.

The agent's first reply notes that Wonder isn't affiliated with Conductor or Meta and that it copies your own files. Agents can make mistakes, so read its plan before you approve it, and check the copy in the **Changes** panel.

## Continue a Claude Code chat

Click the new worktree in the sidebar, then **Start chat**. In that chat, type `/resume` on its own and pick the chat; anything typed after it is lost. It's marked **continues in this worktree**, and opens in a new chat there with its messages. It's one chat at a time, and Claude Code only.

* **Keep the workspace until you've continued its chats.** Don't delete it or switch its branch, or Wonder stops listing its chats.
* **A continued chat leaves the list.** The original stays as it was.
* **Long chats:** you see the newest 600 messages, and the agent keeps the whole conversation. A transcript over 64 MB shows a note instead of its messages.
* **Model:** a continued chat keeps the model it last ran on. You can change it in the model picker.
* **Messages you didn't type:** Conductor's own instructions and action prompts may look as if you typed them. The agent still works in the worktree.

Claude Code deletes transcripts after 30 days by default, so don't leave this for long.

### If a chat is missing

`/resume` lists chats from workspaces this guide moved. It shows **No terminal conversation found…** if your repository's `origin` is a folder on your computer, not a URL such as GitHub's. It can't match a workspace kept in a custom folder. When the branch has another name in Wonder, it also can't match a rebased worktree, a workspace with commits since the copy, a remote other than `origin`, or a missing `origin/HEAD`.

Go back to the chat that moved your work, and the agent gives you the chat's ID. Run this in the new worktree's terminal, choose **Yes** if Claude Code asks whether to trust the folder, and tell the agent to work in this folder:

```sh theme={"theme":{"light":"github-light","dark":"github-dark"}}
claude --resume CHAT_ID
```

This adds to the original chat, so don't also continue that chat in Conductor.

## Set up your scripts

The agent copies your scripts to the repository's main folder, where Wonder reads them. Add scripts from `~/.conductor/settings.toml` by hand in **Repository settings**.

In the repository's **⋯** menu, open **Repository settings**.

1. Under **Worktrees**, click **Use Conductor's setup script** and **Use Conductor's archive script**. Wonder doesn't run them until you accept, and the agent says the setup script is waiting.

   ![Repository settings on Worktrees, with a Use Conductor's setup script button](https://mintcdn.com/wonder-0722b0f6/Q8n4gj6ARZGhn88V/images/migrate-from-conductor/repository-settings-worktrees.webp?fit=max\&auto=format\&n=Q8n4gj6ARZGhn88V\&q=85\&s=d7f3a3e246d86372477abafff58580fc)
2. Under **Files to copy**, list the gitignored files new worktrees need. Write `**/.env.local` for a file at any depth, and `certs/**` for a folder. An entry that matches nothing stops every new worktree in that repository, so don't add a blanket `.env*`.
3. Close **Repository settings**, and click **Start preview** in the worktree. Wonder opens the **Preview** settings with Conductor's run commands filled in. Check them, and click **Save**.

   ![Repository settings on Preview, with Conductor's run command filled in](https://mintcdn.com/wonder-0722b0f6/Q8n4gj6ARZGhn88V/images/migrate-from-conductor/preview-commands-from-conductor.webp?fit=max\&auto=format\&n=Q8n4gj6ARZGhn88V\&q=85\&s=ba51c4476995ce3541759bcb09cd820b)

Scripts get the [variables Conductor's scripts use](https://wonder.design/docs/set-up-the-preview.md). Setup scripts are stopped after 10 minutes, and archive scripts after 60 seconds.

## What's different in Wonder

Conductor's names and shortcuts come from [its docs](https://www.conductor.build/docs), checked on November 6, 2026.

| In Conductor | In Wonder |
| - | - |
| Workspace | **Worktree**. In Wonder's settings, "workspace" means your organization |
| ⌘⇧P create a pull request | The next-step button in **Changes**. ⌘⇧P starts the Preview |
| Plan mode | Set the chat to **Ask** and write "plan first, don't edit" |
| Comment on a diff line | Select the lines in a file, press ⌘L, and write your note in the chat |

## When you've finished moving

Keep `~/conductor` until its chats are continued and you're happy with the copies. Your Claude Code memory stays in Wonder after you delete it, if you've opened Wonder 0.2.233 or later once while `~/conductor` was still there. You don't need to start a chat.

Deleted `~/conductor` before that? Its memory is still on your computer. In the repository's **⋯** menu, open **Repository settings** → **Memory**, and click **Use this folder** next to the folder marked **From Conductor**.

Don't move a Conductor workspace into Wonder's own worktree folder: **Remove repository** deletes what's there.

**On Windows?** Conductor's desktop app is Mac-only, so there's nothing to move from it.

## If something goes wrong

* **The agent says it doesn't have the tool:** update Wonder to 0.2.220 or later, and ask again.
* **The agent doesn't start the move:** send "Move my work from Conductor to Wonder." exactly, in a chat where you haven't asked for anything else.
* **A chat isn't in `/resume`:** see [If a chat is missing](#if-a-chat-is-missing). It may also be older than 30 days, already continued, or from another agent.

Still stuck? [Contact Wonder support](https://wonder.design/docs/support.md).

## Related

* [Move from Conductor by hand](https://wonder.design/docs/migrate-from-conductor-by-hand)
* [Set up the Preview](https://wonder.design/docs/set-up-the-preview.md)
* [Fix Preview problems](https://wonder.design/docs/fix-preview-problems.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.