How to move off Conductor Cloud before it shuts down

When do I need to move by?

Conductor's announcement sets two dates for Cloud:

• November 13, 2026: Conductor Cloud goes read-only. You can read and export, but you can't send messages, so agents can't keep working.
• November 20, 2026: Conductor Cloud shuts down, and Conductor starts deleting Cloud user data.

The Mac app keeps working until early 2027. What happened to Conductor has every date.

How do I export from Conductor?

1. Move single workspaces to your Mac. Right-click a cloud workspace and choose Transfer to local.
2. Export everything. Go to Settings, then Account, then Export data.
3. Push branches you still need. Each Conductor workspace is its own git branch. Push the ones with unmerged work to GitHub, so nothing lives only in Conductor.
4. Save your repo settings. Copy .conductor/settings.toml if your repo doesn't track it. Secrets usually sit in .conductor/settings.local.toml, which shouldn't be committed.

Buildful can't import Conductor's chat history, so keep the export for reference.

What do I need to carry over?

Conductor keeps a repo's setup in .conductor/settings.toml (scripts docs, environment variables docs). These parts matter wherever you go next:

• The setup script (setup = "pnpm install"). It runs when Conductor creates a workspace.
• The run script (run = "pnpm dev"). It starts your app when you click Run.
• The archive script. It runs before Conductor archives a workspace.
• Environment variables under [environment_variables], plus secrets in settings.local.toml.
• Conductor's own variables. Cloud workspaces set CONDUCTOR_ROOT_PATH and CONDUCTOR_WORKSPACE_PATH, but not CONDUCTOR_PORT or CONDUCTOR_DEFAULT_BRANCH, which only the Mac app sets. No other tool sets any of them, so replace them in your scripts.

How do I set up the same repo in Buildful?

Buildful is a cloud coding agent: each task runs in its own sandbox and ends in a pull request. Connect your GitHub repo, open Repos, and choose Configure on the repo. Here's where each piece of your Conductor setup goes:

Then start a task. Several tasks can run at once, each in its own sandbox, and you can also start them from Slack, Linear or iMessage.

What can't I bring over?

• Chat history. Buildful can't import Conductor's chats.
• The Mac app's local worktrees. Buildful works in the cloud. If you want agents on your own Mac, pick a desktop app instead; Conductor alternatives lists both kinds.
• Signing in with a ChatGPT or Claude plan. Buildful picks the right open-weight model for each task. You can pick a frontier model yourself, with prepaid credit or your own API key.

Where Buildful fits

Buildful does Conductor Cloud's job: agents that keep working with your laptop closed, one sandbox per task, ending in a pull request. Once the repo settings above are filled in, every task starts from them. Smart Mode picks the right open-weight model for each task. On Pro and Team, you can also pick a frontier model like Claude or GPT, with prepaid credit or your own API key. Pro is $10 a month for 1,000 tasks, and Team is $40 for 3,000 shared by the team (pricing). Buildful vs Conductor has the full comparison, and Conductor alternatives lists other cloud agents.

Frequently asked questions

When does Conductor Cloud stop working?

Conductor Cloud goes read-only on November 13, 2026, and shuts down on November 20, 2026. After November 13 agents can't take new messages.

How do I export my Conductor Cloud workspaces?

Right-click a cloud workspace and choose Transfer to local, or export everything from Settings, Account, Export data. Do it before November 20, 2026.

Can I keep my Conductor chats?

Yes, as an export. Use Settings, Account, Export data before November 20, 2026. Push any branch with unfinished work to GitHub too, since the chats don't contain your code.

What replaces Conductor's setup script?

Most coding agents have a setup step that runs after they clone your repo. Copy the commands from the setup line of .conductor/settings.toml into it, in the same order.

Do my CONDUCTOR variables carry over?

No. Only Conductor sets them. Cloud workspaces had CONDUCTOR_ROOT_PATH and CONDUCTOR_WORKSPACE_PATH, while CONDUCTOR_PORT and CONDUCTOR_DEFAULT_BRANCH were set only on the Mac. Replace any you use in your scripts.