Migrate from Conductor to MightyMouse, step by step
Conductor Cloud is going away, and you do not want to start every project from a blank chat.
Short answer: To migrate from Conductor, install MightyMouse on the Mac where Conductor ran and open the Code area. Your workspaces appear under From Conductor, and Continue here starts a Claude session that already knows how the old chat ended.
Conductor has said its cloud goes read-only on November 13 and shuts down on November 20 (source: conductor.build/announcement). If you want the full picture of what that means, read what the Conductor shutdown means for your workspaces. This page is the practical part: how to get your work moving again.
MightyMouse reads the workspace list Conductor keeps on your Mac. You pick one, press a button, and a new session starts in the same folder with the end of your old chat pasted in. Nothing is uploaded to do this.
Step 0: bring cloud workspaces onto your Mac first
This is the step people miss. MightyMouse can only see what is stored on your Mac. A workspace that lives only in Conductor Cloud has nothing local to read, so it will not show up. Move those to local while the cloud is still readable, which means before November 13 if you can.
Step 1: get the Mac app and sign in
Install MightyMouse, the Mac app that turns your iPhone into a trackpad, keyboard and agent remote on the same Mac that ran Conductor. Open it and sign in. It has to be the same Mac, because the import looks in Conductor's folder on that machine.
Step 2: turn on Advanced if you cannot see Code
A brand new install starts in a simple mode with just the phone trackpad and voice typing. The Code area is hidden there. Open Settings and switch on the toggle labelled "Advanced - show chat, building and agent tools". Its own description says that on, you get "Chat, Code, Jobs and everything else". If you had MightyMouse before, this is probably on already.
Step 3: open From Conductor
In the Code area, under your projects, a small button reads "From Conductor" with a number beside it. The number is how many workspaces it found. Click it and the list opens. If MightyMouse finds none, the button does not appear at all.
- Each row shows a title: the first line of the first message you sent in that workspace, cut to 80 characters.
- Under it you see the repo, the branch and how long ago it changed. The newest are first.
- Archived workspaces are in the list too, so scan for the ones you still care about.
Step 4: press Continue here
Press "Continue here" on a row. The button says "Starting..." and then the row reads "Started - find it in your list". The session appears with your other sessions.
Here is what that session starts with:
- A Claude Code session opened in the old workspace folder. If that folder is gone, it opens in the repo itself and is told to switch to your branch.
- The end of your old chat: up to the last 12 messages, each trimmed to 400 characters, 6,000 characters in total.
- A last line telling it to pick up where you left off.
If something goes wrong, the row shows the reason and the button turns into "Try again". If the workspace was deleted from your Mac since you opened the list, you will see "That Conductor workspace is no longer on this Mac."
Step 5 (optional): approve and merge from your phone
Once your sessions run in MightyMouse, you can pair your phone and check on them from the couch. Each session shows its Changes (files, lines added and removed). You can open a pull request, and merge it once GitHub says it is ready, on the Mac or on the phone. This uses the GitHub command line tool, so it needs to be on your Mac and signed in.
You can also turn on lid-closed mode, which keeps the Mac awake with the lid shut so a running agent is not cut off. MightyMouse will not turn it off while an agent is still working.
What does not come over
Be clear about this before you rely on it. The import reads three things from Conductor's local database: your workspaces, your repos and your chat messages. That is all.
- Cloud-only workspaces. No local copy, nothing to read.
- Environment variables and secrets. The import never touches them, so set them up again.
- Routines. These are not read. The nearest thing is a MightyMouse job that fires when a pull request or issue is opened, or when checks fail on a pull request. You set those up yourself.
- Your full chat. Only the tail comes across, and only the text. Tool calls and file contents from the old session are left out.
- The same agent. Continue here always starts Claude Code. Codex, Cursor and OpenCode are available in MightyMouse, but you choose them for new sessions.
The honest tradeoff
You are not moving a session, you are starting a new one that has read the end of the old one. It remembers the last stretch of the conversation, not the whole project. Expect to re-explain anything from early in a long chat. And you give up Conductor's own app: MightyMouse is a Mac app with a phone remote, so if you liked Conductor's layout, it will feel different. If you are still choosing, the Conductor alternatives compared and the MightyMouse vs Conductor page lay out what each one does.
Keep your Conductor work going, from your Mac or your phone.
Free to try. Your chats stay on your Mac.
Common questions
How do I migrate from Conductor?
Install MightyMouse on the Mac that ran Conductor, sign in, and open the Code area. Click From Conductor, then press Continue here on each workspace. A Claude Code session starts in the same folder with the end of your old chat.
Can I export my Conductor workspaces?
MightyMouse does not make an export file. It reads the workspaces Conductor already stores on your Mac and lists them, read-only, so your Conductor data is not changed.
How do I move Conductor Cloud workspaces to local?
Do that inside Conductor before the cloud closes. MightyMouse can only see workspaces stored on your Mac, so a cloud-only workspace will not appear in From Conductor until it is local.
Why is there no From Conductor button in MightyMouse?
Two reasons. The Code area is hidden until you turn on Advanced in Settings. And the button only shows when MightyMouse finds Conductor workspaces on this Mac, so it will not appear on a Mac that never ran Conductor.
Do my Conductor environment variables and routines transfer?
No. The import reads workspaces, repos and chat messages only. Set your environment variables up again, and use a MightyMouse job that fires on a new pull request, a new issue or failed checks in place of routines.
When does Conductor Cloud shut down?
Conductor has said the cloud goes read-only on November 13 and shuts down on November 20, per its announcement at conductor.build/announcement.
Ready to move? MightyMouse turns your iPhone into a remote for the Mac that runs your coding agents, so you can approve and merge from anywhere.