Conductor is joining Meta. If you run your coding agents in it, here's what changes and when, what to save first, the alternatives, and why Moontors is the one to pick.
Disclosure: I build Moontors. Everything about the other tools comes from their own pages, checked on November 7, 2026.
What happens to Conductor, and when
From Conductor's announcement:
- November 4: no new sign-ups or downloads. Free users can't upgrade, and Pro users keep Pro's features for free.
- November 13: Conductor Cloud goes read-only. You can read old chats and export data, but not send messages. Active subscribers get a refund.
- November 20: Conductor Cloud shuts down, and its user data starts being deleted.
- Early 2027: the Mac app, which gets new models and critical bug fixes until then, winds down, and its user data is deleted.
Before November 13: save your work
- Cloud workspaces: right-click each one and choose Transfer to local, which moves it and its chats to your Mac.
- Your chats: Settings → Account → Export data downloads all of it.
-
Local workspaces are git worktrees, each on its own branch, usually under
~/conductor/workspaces/<repo>/<workspace>. Their commits are already in your repository: commit what you want to keep, and push each branch (git push -u origin <branch>).git worktree listshows them all. - Anything built on Conductor's API: it manages cloud workspaces, so it goes with the cloud.
The alternatives
Every one of these runs on a Mac too.
| Tool | Windows | Linux | Agents |
|---|---|---|---|
| Moontors | Yes | Yes | Claude Code, Codex, Gemini CLI and Grok Build, in its own interface, never a terminal |
| Paradev (was Superset) | Not yet | Experimental | 21 listed |
| Orca | Yes | Yes | Any CLI agent, ~40 set up |
| Emdash | Yes | Yes | 35 agent CLIs |
| Claude Code Desktop | Yes | Beta | Claude Code |
| ChatGPT app (Codex) | Yes | Preview | Codex |
| Google Antigravity | Yes | Yes | Its own agent |
- Paradev is the closest in shape, a workspace per task, and open source under MIT since November 4. It needs an account, isn't on Windows yet, and its iPhone app needs Paradev Pro.
- Orca and Emdash are open source and run dozens of agent CLIs, Cursor and OpenCode among them.
- Claude Code Desktop and the ChatGPT app each run one vendor's agent, with that vendor's cloud.
- Google Antigravity runs Google's own agent, rather than Claude Code or Codex.
Why Moontors
- A real interface, not a terminal. Conductor gave you chats rather than a command line, and so does Moontors, for every agent it runs: it drives each one through the agent's own protocol, so you read its replies, answer its permission requests and pick its model in Moontors' own views, each session a live card on one board.
- Your agents keep working when you close the app. In Conductor, that took its cloud, and local sessions end when you close the app. Moontors keeps every session working in a background service on your own computer, with no cloud to pay for or to lose.
- Answer them from your phone. The Android app pairs with your computer directly to follow and answer your sessions, and the iPhone app is coming soon.
- Claude Code and Codex on your own plans, Claude Code on your Claude subscription and Codex on your ChatGPT sign-in, beside Gemini CLI and Grok Build.
- Agents that work together. A Claude Code session can hand work to a Codex session and hear back.
- Free, with no Moontors account, for everything on your computer and the phone on your own network. Pro, $20 a month, adds your phone's notifications and reaching your computer from anywhere, through a relay that carries the link without reading it.
- Mac, Windows and Linux, the same app on all three.
- Your worktrees come with you. Add your repository as a project, and the worktrees Conductor made are in its Git view, each ready to start a session in.
Moving to Moontors, step by step
- Install it from moontors.com and sign in to your agents. Moontors installs an agent the first time you sign in to it. (Signing in)
-
Add your repository as a project, the same folder Conductor used. A session in any worktree of that repository counts under the project, wherever the worktree is,
~/conductor/workspaces/included. (Projects) - Pick up a Conductor workspace: open the project's Git view. Every worktree of the repository is in its left column; its +, or Start a session here, starts a session in that worktree's folder.
-
Start new work with Run in a new worktree in Create session, and name a branch if you want one. Moontors puts the worktree in
~/.moontors/worktrees/and copies in the files your project lists, such as.env. (Worktrees) - Leave Conductor's folders alone until every workspace you need has been picked up and its branch pushed.
Good to know
- Your Conductor chats stay in Conductor, so export them before you go.
- Cursor and OpenCode are coming soon; today Moontors runs Claude Code, Codex, Gemini CLI and Grok Build.
- Setup scripts in
conductor.jsondon't carry over: list the files a new worktree needs, and Moontors copies them in. - Moontors' Git view commits, pushes and pulls, and your agent opens the pull request when you ask it to.
If you're moving from Conductor and something here doesn't fit how you worked, tell me in the comments.
AI did the writing, I did the reading, and we both took credit.
Top comments (0)