On November 4, Conductor announced that it is joining Meta. As part of that, Conductor Cloud, the hosted version of Conductor where agents run in shared cloud workspaces, is closing this month. Active subscribers get a refund, and the local Mac app keeps working for now.
If your team relied on Conductor Cloud, you need somewhere else for agents to keep running after you close your laptop. This post explains how to move that setup to Replicas: what to save before Conductor Cloud goes read-only, how each part of a Conductor Cloud organization maps to Replicas, and the few places where the two work differently. The step-by-step checklist lives in the docs at Migrate from Conductor Cloud.
Conductor Cloud shutdown dates
These dates come from Conductor's announcement and changelog.
| Date | What changes |
|---|---|
| November 4, 2026 | New sign-ups stop. |
| November 13, 2026 | Conductor Cloud becomes read-only. You can read old chats and export data, but you can't send new messages. |
| November 20, 2026 | Conductor Cloud shuts down and Conductor begins deleting cloud user data. |
| Early 2027 | The local Mac app stops getting new models and bug fixes and begins winding down. |
Migrate with your coding agent
Most of the migration is reading one configuration and writing another, which a coding agent can do for you. Paste this prompt into Claude Code, Codex, or Cursor on the computer where you used Conductor. The agent reads your Conductor setup, then uses the Replicas CLI to create an environment with the same repositories, setup scripts, variables, and routines. It keeps secret values out of the conversation and lists anything it couldn't find.
The rest of this post explains each step, if you'd rather do it by hand or want to check what the agent did.
What to save before November 13
Anything that exists only in a cloud workspace disappears with the service, so the first job is to get it out. Work through this list while the workspaces still accept commands:
- Branches. Commit and push every branch you care about, including new files the agent created but never committed.
- Git-ignored files.
.envfiles and local config don't travel with a push. Copy them somewhere safe. - Chats. Use Settings → Account → Export data to download everything, or right-click a workspace and choose Transfer to local to move it and its chats to your Mac.
- Cloud Computer settings. Copy the install software script, each repository's setup script, and the list of variable and secret names. Conductor hides saved values, so you'll get the values themselves from wherever they originally came from.
Replicas can't import Conductor chat history. The export is still worth keeping, because you can paste the relevant part of an old conversation into the first message of a new workspace when the agent needs that context.
How Conductor Cloud concepts map to Replicas
Most of what you configured in Conductor Cloud has a direct counterpart. The biggest structural change is that Conductor Cloud has one Cloud Computer per organization, while Replicas lets you have many environments, each with its own repositories, variables, and setup.
| Conductor Cloud | Replicas |
|---|---|
| Organization | Organization with roles and access |
| Cloud Computer | Environment |
| Install software script | Warm hook |
| Repository setup script | Start hook |
| Environment variables and secrets | Environment variables |
| Cloud workspace | Workspace |
| Routines | Automations |
| Conductor API | API, CLI, and MCP server |
| iOS app | iOS app |
Moving setup scripts
Conductor Cloud splits setup into two scripts. The install software script runs once per Cloud Computer build and handles slow things like system packages and runtimes. Each repository's setup script runs every time a new workspace is created.
Replicas makes the same split with two hooks:
- A warm hook runs ahead of time. Replicas keeps a pool of workspaces that have already run it, so a new workspace starts with dependencies installed instead of waiting for them. Put your install software script and dependency installs here.
- A start hook runs when a workspace is assigned to a task, before the agent starts. Put steps that need to be fresh here, such as starting a dev server or running migrations.
You can set both on an environment in the app, or commit them to the repository in a replicas.json file so every environment that clones the repo uses the same setup:
If your scripts read CONDUCTOR_* variables, remove those references. When a hook fails, the environment page shows the end of the log and a Fix with agent button that starts an agent from the failing script.
Moving variables and secrets
In Replicas, variables belong to an environment. Open the environment, go to Environment Variables, and paste the contents of a .env file into a key field or use Import .env. Replicas marks keys whose names look like secrets, such as API_KEY or TOKEN, as Sensitive, and their values are never shown again after saving. Detection goes by the key name, so check Sensitive yourself on any secret whose name doesn't look like one. If your team keeps secrets in Doppler or Infisical, you can sync them from there instead.
As in Conductor Cloud, you don't need to add a GitHub token. Replicas authenticates Git through its GitHub App.
If you miss a variable, the agent can ask for it. It opens a form above the chat where you paste the value, and you choose whether to save it to the environment for future workspaces.
Continuing open branches and pull requests
For a branch you pushed from Conductor, start a task from Home, pick the environment, choose that branch as the starting branch, and describe what is left to do. For a pull request that is already open, comment @tryreplicas on it in GitHub. Replicas starts a workspace on that pull request, and later comments on the same PR go to the same workspace.
Moving routines to automations
Conductor routines run agents on a schedule or from a GitHub action. Replicas automations cover both, and each automation also lets you choose its environment, coding agent, model, and workspace size.
| Routine trigger | Automation trigger |
|---|---|
| Schedule | Schedule trigger, once or recurring |
| GitHub action | GitHub trigger on pull request events, such as opened, updated, or merged |
Automations can also start from GitLab, Slack, Linear, Sentry, or any system that can call a webhook. To recreate a routine, copy its prompt into a new automation, pick the environment you set up above, and add the trigger.
Agents and team
Conductor runs Claude Code, Codex, and Cursor agents. Replicas runs those three plus Muse Code, Opencode, and Pi. You can keep using your existing subscriptions or API keys: connect them once as credentials, either for yourself or shared with the organization.
Invite teammates from the Members page and use roles to decide who can read or change each environment. To bring a teammate into a workspace, share it with Cmd/Ctrl + Shift + S, which also copies its link.
What works differently
A few things change in ways worth knowing before you switch:
- More than one setup. You can have separate environments for different repositories or teams, plus personal environments for your own tokens. An environment can fork another and override only what differs.
- More places to start work. Besides the web, desktop, and iOS apps, you can start agents from Slack, Linear, GitHub comments, and the API.
- GitLab. Conductor Cloud supports GitHub repositories. Replicas supports GitHub and GitLab.
- A desktop the agent can use. Every workspace has a Linux desktop with Chrome that the agent can drive to test its changes, and that you can watch or control from the app.
- Usage-based billing. Each plan includes usage, and workspaces are billed per minute only while they are awake.
The full checklist, with links to each setting, is in Migrate from Conductor Cloud. If you get stuck partway through, email us at founders@replicas.dev.