How to move from Conductor to Murmell
Your Conductor workspaces are git branches, so nothing is locked in: push them, open the repository on Murmell, and your agents carry on in the cloud with the same Claude Code and Codex accounts. Conductor users skip the access queue and get their first month back in Claude credits.
Step by step
- Push every workspace branch. Each Conductor workspace is a git worktree on its own branch. Commit what is in flight and push the branches to GitHub, GitLab or Bitbucket. On Conductor Cloud, do it before November 13, when workspaces become read-only.
- Request access as a Conductor user. Fill in the access request and mention Conductor. You skip the queue: we open your account the same day, and your team with it.
- Open the repository on a canvas. Import the repository you pushed. The canvas starts a cloud machine with Claude Code, Codex and the usual tools already installed, so nothing has to be set up on your laptop.
- Connect your agents and run them side by side. Sign in with your own Anthropic and OpenAI accounts, the subscriptions you already used in Conductor. Open as many agents as your plan allows on the same project: they claim a file before they write to it, so they do not overwrite each other.
What changes with Conductor
Conductor announced on November 4, 2026 that it is joining Meta. The hosted Conductor Cloud becomes read-only on November 13 and shuts down on November 20. The Mac app keeps running for a few months, and in early 2027 it stops getting new models and critical fixes. If your agents ran in Conductor Cloud, you have two weeks to move them.
What you get by migrating
| Conductor | Murmell | |
|---|---|---|
| Where agents run | Your Mac. Conductor Cloud closes on November 20 | A cloud machine that keeps going when your laptop closes |
| Orchestration | One worktree per agent, merged by you at the end | One shared directory. Agents claim files and message each other, Claude Code to Codex and back |
| Tokens and speed | Each agent rebuilds its context in its own copy | Half the tokens and 1.4x faster delivery |
| Your team | Whoever sits at that Mac | Everyone on the same canvas, live, with a name on every cursor |
| Platforms | macOS | Any browser |
| New models | None from early 2027 | As soon as they ship |
Why Murmell is the closest move
Conductor Cloud ran your agents away from your laptop. So does Murmell: every project runs on a cloud machine, the terminals keep going when you close the tab, and the output is there when you come back. It works with the agents you already use: Claude Code, Codex, Kimi and OpenCode, on your own accounts.
What you gain on the way is the room. A canvas is multiplayer: a teammate opens the link and sees the same windows and terminals move live, with a name on every cursor. Several agents work on one project directory, and an agent claims a file before it writes to it, so there is no pile of branches to merge at the end. Murmell and Conductor side by side.
Your first month back, in Claude credits
Request access and say you used Conductor. We open your account the same day, for you and your team, and we give your first month back as Claude credits. Want to see it first? Ask for a demo in the same form and a founder will run it on your own repository.
Conditions
For people and teams who used Conductor or Conductor Cloud before November 4, 2026, and who request access by December 31, 2026, mentioning Conductor. The credit equals the price of the first paid month of a Murmell plan, is added as Claude usage on Murmell once that month is paid, and is valid for three months. One credit per account or per team. It is not paid out in cash and cannot be transferred. We may ask for proof of a Conductor account.
Straight answers
When does Conductor stop working?
Conductor announced it is joining Meta on November 4, 2026. Conductor Cloud becomes read-only on November 13 and shuts down on November 20. The Mac app keeps working for now, and in early 2027 it stops receiving new models and critical fixes.
Can I bring my Conductor workspaces and branches?
Yes. Conductor keeps each workspace as a git worktree on its own branch, so once the branches are pushed they open on Murmell like any other repository. Chat history stays behind: it lives in Conductor's own database.
Do I keep using my own Claude Code and Codex subscriptions?
Yes. Murmell launches the real CLIs with your own accounts. We charge for the machine and the room, never for the model.
What is different from Conductor?
The agents run on a cloud machine instead of your Mac, so they keep going when the laptop closes. They share one project directory instead of one worktree each, and teammates can open the same canvas and watch them work live.
Can my team get a demo?
Yes. Ask for one in the access form and a founder will show you Murmell on your own repository, then open access for the whole team.