Conductor Cloud is shutting down: how to move to boxes.dev
Conductor announced on November 4, 2026 that its team is joining Meta. Conductor Cloud will become read-only on November 13 and shut down on November 20, so teams that run agents in Conductor's cloud workspaces have about two weeks to save their work and move it somewhere else.
This post covers what's changing, how to save your work from Conductor Cloud, and how to move your projects to boxes.dev, which runs Claude Code and Codex on cloud machines that hold your full development environment.
What's changing and when
Conductor's announcement lists these dates:
- November 4: Conductor stopped accepting new sign-ups and app downloads, and free users can no longer upgrade to Pro. Pro users can keep using Pro features for free.
- November 13: Conductor Cloud will become read-only. You'll be able to read old chats and export your data, but you won't be able to send new messages. Active subscribers will get a refund.
- November 20: Conductor Cloud will shut down, and Conductor will start deleting Cloud user data.
- Early 2027: Local Conductor will keep getting new models and critical bug fixes until early 2027, when it will start winding down.
Save your work from Conductor Cloud
You'll still be able to export your data while Conductor Cloud is read-only, but after November 13 you won't be able to give an agent new instructions. Finish or save any work in progress before then:
- In each cloud workspace, commit and push the branches you want to keep.
- To move a workspace and its chats to your Mac, right-click it and choose Transfer to local.
- To download an archive of all your data, open Settings → Account → Export data.
- Copy your Cloud Computer's install script and each repository's setup script, and list the environment variables and secrets your workspaces use. You'll need them to set up the same environment somewhere else.
How boxes.dev compares with Conductor Cloud
Boxes.dev runs Claude Code and Codex with your Claude or ChatGPT login or an API key, so you can keep the agent accounts you used in Conductor. It works with the same GitHub repositories and pull requests.
The main difference is how the cloud environment is set up. Conductor Cloud builds each workspace from your scripts. Boxes.dev first prepares a Template box, a cloud machine where your app runs with its tools, databases, services, and data, and saves it as a snapshot. Each task then runs on its own devbox, a full, isolated copy of the Template box, so the agent can run your app and test its changes the way an engineer would.
Most of what you used in Conductor Cloud has a counterpart in boxes.dev:
| In Conductor Cloud | In boxes.dev |
|---|---|
| The Cloud Computer, built from an install script | The Template box, which a setup agent prepares from your laptop or a GitHub repository, saved as a snapshot and kept current by an optional maintenance script |
| A setup script for each new workspace | A startup script for each new devbox |
| A microVM for each workspace, which can hold several chats | A devbox for each task, which can hold several threads |
| Workspaces that sleep after four hours without activity and keep their files | Devboxes that sleep when nobody is using them and keep their files and memory, so dev servers and databases resume when they wake |
| Organization environment variables and secrets, with repository and personal overrides | Environment files with project, team, and personal values |
| Ports forwarded to your Mac, and preview URLs | Ports forwarded to your laptop, a browser you share with the agent, public links, and Project URLs |
| Shared workspaces that teammates can open and prompt | Read-only thread links and team-wide thread reading, plus @boxes.dev in Slack, where teammates you allow can start work that runs with your access |
| The Conductor API and routines that run on a schedule or from a webhook | Automations that run on a schedule or from an API call, and agents that start other agents on new devboxes |
| The iPhone app | iOS and Android apps with a terminal |
For a detailed comparison, see Boxes.dev vs Conductor.
Move a project to boxes.dev
- Sign up at boxes.dev/conductor and connect Claude Code or Codex with the account you used in Conductor, or with an API key. See Connect Codex and Claude.
- Create a project. To copy a working environment from your Mac, including the environment files and local databases you approve, use local-folder setup in the desktop app. To start from your repositories instead, create the project from GitHub.
- Give the setup agent your Conductor install script, either in a setup note or by pasting it to the agent on the Template box, so it can install the same tools and get your app running.
- Move the commands that should run on every new devbox, such as starting services, into the startup script. Each devbox starts as a copy of the Template box, so dependencies you install there will already be on every new devbox.
- Add the environment variables and secrets from your list to environment files.
- Start a task from the desktop app, your phone, the CLI, Slack, or Linear. See Your first task.
New teams that sign up at boxes.dev/conductor will get their first month of Pro free, including 300 box-hours, with no card required. Pro will end after that month unless you choose to keep it. Paid plans start at $19 per user each month; see Plans, seats, and box-hours.
If you still use Conductor on your Mac
Local Conductor will keep working until early 2027, so you don't need to move everything at once. You can keep running local workspaces in Conductor and use boxes.dev for the tasks you ran in Conductor Cloud, such as work that should keep going after you close your laptop or that needs your app's full environment.
For more on the day-to-day workflow, read how boxes.dev works, or see how boxes.dev compares with other tools.