Get Started
Migrate from Conductor Cloud
Move your Conductor Cloud workspaces to Paradev before Conductor Cloud shuts down
Conductor is joining Meta, and Conductor Cloud is shutting down. This guide gets your cloud work out of Conductor and into Paradev, either on your Mac or in a Paradev cloud workspace.
Conductor Cloud's timeline
- November 13, 2026: Conductor Cloud goes read-only. You can still read chats and export data, but you cannot send messages to agents.
- November 20, 2026: Conductor Cloud shuts down and Conductor begins to delete cloud data.
Work that exists only in a Conductor Cloud workspace is not on your machine. Move every workspace you want to keep before November 20.
For the local Conductor app, see Migrate from Conductor.
What Maps to What
| Conductor Cloud | Paradev |
|---|---|
| Cloud workspace | Cloud workspace |
| Cloud setup: repositories, variables, secrets | Environment with variables |
| Setup script and actions | .paradev/config.json (lifecycle scripts) |
| Routines | Automations with Cloud as the device |
| iOS app | iPhone and iPad app |
| Cloud organization | Paradev organization. Environments are visible to the whole organization by default |
1. Save Your Work in Conductor
Do this first, before November 13 if you can.
- Push every branch. In each Conductor Cloud workspace, commit all changes, including new files (
git add -A), and push the branch. A pushed branch is safe on GitHub whatever you choose next. A push does not include Git-ignored files, such as.envfiles or local data. Copy out any you need before November 20. - Export your data. In Conductor, go to Settings → Account → Export data. This keeps a copy of your chats. Paradev cannot import Conductor chats, so this export is your record of them.
Then pick where to continue: on your Mac, or in a Paradev cloud workspace.
2a. Continue on Your Mac
- In Conductor, right-click the cloud workspace and choose Transfer to local. Conductor moves the workspace and its chats to your Mac.
- Follow Migrate from Conductor to import the workspace into Paradev and convert your scripts.
If you only pushed the branch, add the repository in Paradev and create a workspace from the Existing branch instead. See Workspaces.
2b. Continue in a Paradev Cloud Workspace
Paradev cloud workspaces keep agents working when your laptop is closed, and you can open them from desktop, iPhone, or iPad. They need a paid plan, and the GitHub repository must be shared with the Paradev GitHub App. See Requirements.
Cloud workspaces are in early access. If you do not see Cloud in the device picker yet, continue on your Mac (2a) for now.
Add your setup scripts
Cloud workspaces run the setup scripts in .paradev/config.json from the repository. Convert your Conductor setup script as described in Convert Your Scripts, then commit and push the file to every branch you will use as a base branch. A cloud workspace started from a branch without it does not run your setup.
CONDUCTOR_PORT is not set in Conductor Cloud, so cloud scripts usually do not need a port change.
Create an environment
- Open Settings → Environments and click New environment.
- Add the repositories your Conductor Cloud workspaces used. The first one is the primary.
- Click the environment and add the variables and secrets your Conductor Cloud setup used.
Do not add agent API keys or GitHub tokens. Cloud workspaces ignore them: agents use your sign-in from Settings → Agents, and GitHub access comes from your connected GitHub account. See Credentials.
Not sure what the project needs? Click Set up with an agent in Settings → Environments. Claude installs what the project needs and writes its .paradev/config.json.
Continue each branch
- Press ⌘N and pick Cloud in the device picker.
- Pick the project and the environment.
- Choose the branch you pushed from Conductor as the base branch. Paradev creates a new working branch from it, so an open pull request for the Conductor branch does not get the new commits. Open a new pull request from the new branch, or merge it into the old one.
- Tell the agent where to pick up, for example "Continue the work on this branch. Read the last commits and the open PR first."
From the CLI:
superset workspaces create --base-branch <pushed-branch> --agent claude \
--prompt "Continue the work on this branch"If more than one environment has repositories, also pass --environment <id>. Run the command without it to see each environment's ID.
When one workspace is fully set up, right-click it and choose Save as environment. New workspaces then start from that snapshot instead of running setup each time. See Save a set-up workspace.
Move your routines
Recreate each Conductor routine as a Paradev automation. Pick Cloud as the device to run each session in a new cloud workspace, and pick the machine size. Automations can run on a schedule or when something happens in GitHub, Slack, Linear, Sentry, and other tools.
3. Check Your Usage
Paradev meters cloud usage in GB-hours: machine memory multiplied by run time. A stopped or sleeping workspace uses none, and a workspace stops by itself after about an hour of no activity. Settings → Billing shows what you have used. See Usage and Billing.
Get Help
Stuck on a step? Ask in the community or see Troubleshooting.