How to migrate from Conductor

Checked against Conductor's announcement and documentation on November 7, 2026. Worktree Kanban is not affiliated with Conductor or Meta.

If you use Conductor Cloud, export your data first. Cloud goes read-only on November 13, 2026, and shuts down on November 20, when Conductor begins deleting Cloud user data. Follow step 1 before anything else.

Your local code is safe: Conductor's local workspaces are ordinary git worktrees and branches, so they do not depend on the app. Worktree Kanban cannot import Conductor's workspaces or chats automatically, so this guide saves what matters first, then moves open work over by hand. Allow about 30 minutes per repository.

What is happening to Conductor

• On November 4, 2026, Conductor announced it is joining Meta. New users can no longer sign up or download the app. Existing users can keep using it for free.
• Conductor Cloud goes read-only on November 13: you can read old chats and export data, but not send new messages. It shuts down on November 20, and deletion of Cloud user data begins. Active subscribers get a refund.
• The local Mac app keeps working for now, with new models and critical bug fixes until early 2027. It then winds down, and Conductor says it will delete all Conductor user data when the app shuts down.

If you only use local workspaces, nothing forces you to move today. The local app has a few months left, so you can move at your own pace. If you use Cloud, the dates above apply now.

What carries over

Check the differences first

Worktree Kanban is not a drop-in replacement, so check these before you start.

You would lose

• Cloud workspaces and multiplayer. Agents run on your own PCs, and the board is kept on one machine. There are no cloud sandboxes and no shared chats, and tasks stop when that machine is off.
• OpenCode. Worktree Kanban runs Claude Code, Codex CLI, Antigravity CLI, Gemini CLI, and Cursor CLI. Approving actions on the card and a few other features work only with some agents.
• The iOS Remote Control app. Worktree Kanban has no mobile app.
• The Conductor API and MCP server for driving workspaces from other tools.
• Settings shared through the repository. Scripts live on each machine, not in a file like .conductor/settings.toml.
• Linked directories across repositories. Each task belongs to one repository. You can keep up to 3 repositories open as tabs.

You would gain

• Windows and Linux. Conductor is available only for macOS. Worktree Kanban also runs on Windows and on Linux (x86_64), including WSL repositories on Windows. Remote control works between Mac and Windows only.
• Checkpoints that also cover Pipelines. Conductor's checkpoints revert a chat turn. Worktree Kanban records a point before each agent run, and restoring returns the files, the Pipeline progress, and the conversation together. It works while a task is stopped in review or has failed, keeps up to 100 points per task, and cannot be undone.
• Pipelines. Describe a flow in plain language, such as "implement with Codex, review with Claude, and go back if changes are needed", and agents hand the work over step by step along a flowchart with branches, loops, and parallel steps.
• Mac and Windows remote control over an SSH tunnel, with no external server.
• No cloud service to depend on. Worktree Kanban keeps its data on your machine. It is source-available under FSL-1.1-ALv2, which excludes competing commercial products and services. Each version also becomes available under Apache 2.0 two years after its release.

Migrate in 6 steps

1. Export Cloud data, if you use it

Use Conductor's official steps, and do this first. If you do not use Cloud, skip this step.

• To download all your data: in Conductor, go to Settings → Account → Export data.
• To move a cloud workspace and its chats to your Mac: right-click the workspace and choose Transfer to local.

Do both before November 13. After that date, the announcement promises only reading old chats and exporting data, until the shutdown on November 20. Check that the exported files open before you move on.

2. Save your work in git

Run this in each repository to list Conductor's worktrees. They are usually under ~/conductor/workspaces/<repo>/<workspace>.

git worktree list

For each worktree you want to keep, commit anything uncommitted and push the branch. A pushed branch can also be picked up from a Windows or Linux machine.

git -C <worktree-path> status --short
git -C <worktree-path> add -A
git -C <worktree-path> commit -m "WIP: move from Conductor"
git -C <worktree-path> push -u origin HEAD

3. Back up local data

Quit Conductor, then copy these folders somewhere safe. Copy your Setup, Archive, and Run scripts from the project's Settings too, unless they are in .conductor/settings.toml. Workspaces can hold files such as .env, so keep the copy private and do not commit it.

4. Install Worktree Kanban

Mac / Linux:

curl -fsSL https://raw.githubusercontent.com/kazuya83/worktree-kanban/main/install.sh | bash

Windows (PowerShell):

irm https://raw.githubusercontent.com/kazuya83/worktree-kanban/main/install.ps1 | iex

Or download it from Releases. The builds are not signed or notarized, so your OS may warn you the first time. Install and sign in to the CLI of each agent you use, then open your repository and choose your agents under "Agents to use" in Settings. Add your scripts under "Branches and landing", replacing any CONDUCTOR_ variables with the names in the table above.

5. Move open work

• Work that is nearly finished: finish it from the worktree or branch in your terminal, and merge it or open a PR as usual.
• Work that needs more agent time: set "Base branch" to that workspace's branch under "Branches and landing", then create a task. Its worktree starts from that branch. The merge target defaults to the same branch, so choose your main branch in the merge dialog if you want to land it directly. Then set "Base branch" back.
• Issues not started yet: create tasks by hand, or use the Issue tab under "+ New task" for GitHub, GitLab, Linear, and Jira.

The agent does not see the Conductor chat, so write what is done and what is left in the new task.

6. Clean up

Once everything is merged or pushed, archive the workspaces in Conductor or remove the worktrees yourself, along with any branches you no longer need. git branch -d refuses to delete a branch that is not merged.

git worktree remove <worktree-path>
git branch -d <branch-name>
git worktree prune

If you are unsure, do this later. Keep Conductor installed until you are done, because it can no longer be downloaded.