If you run coding agents in Conductor Cloud, move every cloud workspace you care about to your Mac and download your data before Friday, November 13, 2026. On that day cloud workspaces turn read-only, and on Friday, November 20 Conductor starts deleting Cloud user data. Conductor built two buttons for this: right-click a cloud workspace and choose Transfer to local to bring it and its chats onto your Mac, and go to Settings → Account → Export data to download an archive of everything. The local Mac app keeps working for now and will get new models and critical bug fixes until early 2027. This guide explains what changes on which date, walks through both buttons, lists the things the buttons do not cover (your cloud setup script, environment variables and running processes), and points to where you can run cloud agents next.

Everything below was checked on November 5, 2026 against Conductor’s own announcement, the Conductor changelog entry for version 0.93.0 (November 4, 2026) and Conductor’s documentation on Conductor Cloud, cloud workspaces, the Cloud FAQ and the general FAQ. TechCrunch confirmed the deal with Meta the same day.

Key facts:

• November 4, 2026: no new sign-ups and no app downloads for new users. Existing free users can’t upgrade to Pro, and Pro users keep Pro features for free. (announcement)
• November 13, 2026: Conductor Cloud goes read-only. You can still read old chats and export data, but you can’t send new messages. Active subscribers get a refund. (announcement)
• November 20, 2026: Conductor Cloud shuts down and Conductor begins deleting Cloud user data. (announcement)
• Early 2027: local Conductor stops getting new models and critical bug fixes and starts winding down. Conductor says it will delete all user data when the app shuts down. (announcement)
• The two tools: right-click a cloud workspace and choose Transfer to local; for a full archive, use Settings → Account → Export data. (changelog)

What happened

Conductor is the Mac app that lets you run several coding agents (Claude Code, Codex, Cursor and OpenCode) side by side, each in its own workspace with its own branch, files, terminal and diff. On November 4, 2026 its founder Charlie Holtz announced that “Conductor is joining Meta”. TechCrunch reported that Meta confirmed the acquisition but gave no further details.

The announcement says the team is building “the next interface” and hopes to have “something new for you to use early next year”. Until then, Conductor “will keep working as normal”, with one exception: Conductor Cloud, the paid feature that runs agents in cloud sandboxes instead of on your Mac, shuts down “over the next few weeks”.

So there are really two stories here:

1. Conductor Cloud users have a hard deadline in about two weeks. That is what most of this guide is about.
2. Local Conductor users can keep working, but should start planning for early 2027, when the app winds down.

Who needs to act now

You need to do something before November 13 if any of these apply:

• You have cloud workspaces (they run in a Linux sandbox rather than on your Mac) with work you have not finished, merged or pushed.
• You or your team used Multiplayer to share cloud workspaces and chats across your organization. The Cloud docs say cloud workspaces and chats are shared with the whole organization, so each person should check the workspaces assigned to them.
• You want to keep the chat history of your cloud agents. Conductor’s Cloud FAQ says that, unlike local sessions, chat messages from cloud workspaces are stored on Conductor’s servers. Those are the servers that start deleting data on November 20.
• You configured a Cloud Computer (your organization’s shared cloud environment, with its repositories, environment variables, secrets and installed software) and would like to rebuild that setup somewhere else later.
• You pay for Conductor and want to know about your money. The announcement says active subscribers will get a refund, and the FAQ repeats that people who just subscribed can get one too. For questions it gives one contact: support@conductor.build.

If you only ever used local workspaces on your Mac, nothing changes this month. Skip to What happens to local Conductor.

The timeline, in plain language

Conductor’s announcement does not give a time of day or a time zone for these dates, so treat each one as the start of that day and finish well before it.

Date (2026)	What changes	What you can still do
Wednesday, Nov 4	No new sign-ups or app downloads for new users. Free users can’t upgrade. Pro users get Pro features free.	Everything, including cloud agents.
Friday, Nov 13	Conductor Cloud goes read-only. Refunds for active subscribers.	Read old chats and export data. You can’t send new messages.
Friday, Nov 20	Conductor Cloud shuts down. Deletion of Cloud user data begins.	Don’t count on anything in the cloud after this.
Early 2027	Local Conductor starts winding down; updates stop.	Use the local app until then.

The practical deadline is November 12. That is the last day you can still send messages, which means it’s the last day you can ask a cloud agent to finish a task, commit its changes or push a branch. After that, all you can do is read and export.

Step 1: Finish or park the work that is still running

Before you move anything, get each cloud workspace into a clean state. This step is not in Conductor’s instructions; it’s a precaution we recommend, because work you haven’t committed and pushed only exists inside a sandbox that’s going away.

1. Open each cloud workspace you care about. In the Conductor Mac app, cloud workspaces sit in the same sidebar as local ones. Choose Home to see all of your organization’s workspaces, and filter By to yourself so you see the ones assigned to you.
2. Wake it up if it’s asleep. The cloud workspace docs say a cloud workspace goes to sleep after 20 minutes without agent or terminal activity, and opening it wakes it automatically. If it shows Unresponsive, click the workspace name in the top bar to open its details and click Restart.
3. Let any running agent finish, or stop it. Every sandbox also stops at a maximum lifetime of 23 hours and 50 minutes, even when it’s active, and that can cut off a running agent turn. If a turn was interrupted, resend it.
4. Ask the agent to commit and push. In the workspace chat, type something like: “Commit all of your changes with a clear message and push this branch to GitHub. Then tell me the branch name and whether a pull request is open.” Conductor’s cloud workspaces only support GitHub repositories, so the branch goes to the same GitHub repo you started from.
5. Note the branch name. Your code on GitHub is not part of Conductor’s deletion. The branch and any pull request stay in your GitHub account.

Doing this first means that even if a transfer fails, your code is safe in GitHub, and what you lose at worst is chat history.

Step 2: Transfer each cloud workspace to your Mac

This is the main tool Conductor built for the shutdown. According to the announcement FAQ, Transfer to local moves a cloud workspace and its chats to your Mac.

1. Open the Conductor app on your Mac.
2. In the sidebar (or in Home), find the cloud workspace.
3. Right-click it and choose Transfer to local.
4. When it finishes, open the new local workspace and check three things: the chats are there, the branch is the one you noted in Step 1, and the files look right.

A few things to know about where it lands. Conductor’s Git worktree docs say local workspaces are usually created under ~/conductor/workspaces/<repo name>/<workspace name>. Each one is a separate working copy (a “worktree”) of the same repository, with its own branch. A local workspace runs on your Mac with your user permissions; it isn’t a sandbox. The general FAQ says agents in Conductor “run directly on your system without sandboxing.” If your cloud agent was running commands freely because it was inside a throwaway Linux machine, think twice before you give it the same freedom on your own computer. Our guide to Claude Code permission modes explains the safer settings for Claude Code.

Also, local workspaces stop when your Mac sleeps or the app closes. The Cloud docs put it plainly: in a local workspace, “local processes stop” after your Mac closes, while cloud agents kept running until the sandbox slept. Long jobs you used to leave running overnight in the cloud now need your Mac awake and the app open.

Don’t confuse Transfer with Sync

Cloud workspaces had another option called Sync to a local directory, which mirrors the cloud files into a folder on your Mac. The docs warn that sync is one-way, cloud to Mac: “local changes don’t sync back and may be overwritten.” It is not a migration tool. Use Transfer to local instead.

Step 3: Export a full archive of your data

Transfer moves one workspace at a time. To get everything in one download, the changelog and announcement point to:

Settings → Account → Export data

Do this even if you transferred every workspace. It’s a backup that doesn’t depend on the Conductor app keeping working. Save the file somewhere outside the ~/conductor folder, for example in your Documents folder or a cloud drive, so it doesn’t get deleted along with the app later.

You can still export after November 13, because the announcement says read-only workspaces still allow exporting data. Don’t wait for that, though. November 20 is when deletion starts, and the last few days before a shutdown are when support is busiest.

Step 4: Save the setup the buttons don’t move

Your code and chats are covered by Steps 1 to 3. Some of what made cloud workspaces work is stored in your organization’s cloud settings, and Conductor’s docs describe it as separate from local setup. The shutdown notice doesn’t say whether Transfer or Export includes these, so write them down yourself while you can still open the settings:

• The cloud Setup script. The cloud environment variable docs say cloud and local workspaces use separate setup scripts: cloud workspaces run the repository’s Setup script from organization settings, while local workspaces run scripts.setup from .conductor/settings.toml in the repo. If you only ever filled in the cloud one, your transferred workspace may not install dependencies the same way on your Mac. Copy the cloud script text somewhere safe. The docs’ own tip is to commit the script to your repository and call it from both places.
• Cloud environment variables and secrets. Organization-wide values, including secrets, lived in the Cloud Computer environment. Make a list of the variable names you need, and get the secret values from wherever they originally came from (your password manager or the service’s dashboard) rather than copying them around. The docs also say Conductor managed Git and GitHub CLI login for cloud workspaces, so you don’t need to save a GitHub token from there.
• Software you installed on the Cloud Computer. The cloud sandboxes ran Amazon Linux 2023 with Node.js 24, Python 3, git, the GitHub CLI and Google Chrome preinstalled, according to the Cloud FAQ. If you added other tools, write down which ones. Note that your Mac is a different system: the docs point out that Mac-only tools such as Homebrew and Xcode need different steps from Linux.
• Ports and dev servers. Cloud workspaces didn’t get the CONDUCTOR_PORT variable and used Forward ports instead. On your Mac you won’t need the port forwarding; run your dev server the way you normally do.

An easy way to capture all of this without reading settings screens line by line: before November 13, open a cloud workspace chat and ask the agent, “List the setup commands that ran when this workspace was created and every environment variable name you can see (names only, no values). Save the list to a file called SETUP-NOTES.md in the repo, commit it and push.” The environment variable docs say cloud setup scripts, agents and terminals all receive the workspace’s variables, so the agent can see the names. Check the result yourself, and make sure no secret values end up in the file.

What happens to local Conductor

If you use Conductor only on your Mac, here is what the announcement and FAQ say:

• It keeps working normally for now. Local workspaces, chats, diffs and the pull request flow are unchanged.
• It will get new models and critical bug fixes until early 2027. Version 0.93.0, released on November 4, already added GPT-6.1 Terra to the Codex model picker. (We cover that model in our GPT-6.1 Terra guide.)
• It starts winding down in early 2027. Conductor says it will delete all user data when the app shuts down then. For local sessions, the FAQ says session data mostly stays on your device, so it’s worth knowing where it lives (see below).
• Pro features are free for existing Pro users from November 4.
• New users can’t download it any more. The announcement says new users can no longer sign up or download the app. It doesn’t say whether existing users can reinstall, so don’t delete the app or move to a new Mac without a plan.

Where your local Conductor data lives

Conductor’s FAQ gives the exact folders, in its answer about moving to a new computer:

• ~/Library/Application Support/com.conductor.app and ~/conductor: Conductor’s own files, including your workspaces.
• ~/.claude and ~/.codex: where Claude Code and Codex keep their own files.

The FAQ says to copy these only while Conductor, Codex and Claude Code are all closed, and to put them at exactly the same paths on the destination. Its easiest suggestion for a new Mac is Apple’s Migration Assistant. A copy of these folders on an external drive is also a sensible backup before early 2027.

One more detail from the same FAQ: Conductor ships its own bundled copies of Claude Code and Codex (in ~/Library/Application Support/com.conductor.app/bin) and tells you not to update or change them. When you eventually leave Conductor, install Claude Code or Codex separately; don’t try to reuse the bundled ones.

Where to run cloud agents next

Conductor hasn’t said what Meta’s “next interface” will be, only that it hopes to have “something new” early next year. If you can’t wait that long for cloud agents, these are the options we have already written step-by-step guides for:

• Claude Code on the web. If you used Conductor mainly to run Claude Code, Anthropic’s own cloud version works from claude.ai/code or the Claude phone app. It runs on Anthropic’s cloud computers and keeps going after you close your laptop, and it’s included in Pro, Max and Team plans. Our Claude Code cloud setup guide walks through connecting GitHub and picking permissions.
• Google Antigravity Remote Agents. These are Google’s cloud agents for Google AI Pro and Ultra subscribers. Our Jules shutdown guide covers how to start one. That guide was written for a different shutdown, but the move is the same: export first, then rebuild your setup.
• Keep using local Conductor until early 2027. For many people this is the simplest choice: transfer your workspaces, keep your Mac awake for long jobs, and decide later.

Whatever you pick, bring the SETUP-NOTES.md file from Step 4. Most of the work in switching tools is rebuilding the setup script and the environment variables, and you’ll have both written down.

Troubleshooting

The cloud workspace won’t open or says Unresponsive. Click the workspace name in the top bar to open the workspace details, then click Restart. The docs say files and chat history survive sleep; only running processes don’t.

I can’t find Transfer to local. It’s on the right-click menu of a cloud workspace in the sidebar or in Home. Local workspaces don’t have it, because they’re already on your Mac. Make sure your app is up to date: the shutdown changes shipped in version 0.93.0 on November 4.

I missed November 12 and can’t send messages. You can still read chats and export data after the switch to read-only on November 13. Run Settings → Account → Export data right away, and check that your branches are on GitHub. If you need anything beyond that, email support@conductor.build.

My transferred workspace doesn’t build on my Mac. Usually that’s because the cloud Setup script and the local scripts.setup are different (see Step 4), or because a gitignored file such as .env.local didn’t come along. The worktree docs explain that a new worktree starts from tracked files only, and that Conductor’s Files to copy setting handles gitignored files that every workspace needs.

My team shared workspaces through Multiplayer. Who should transfer them? Multiplayer is part of Conductor Cloud, and local workspaces live on one person’s Mac, so agree before November 13 who brings each shared workspace home. The Multiplayer docs say you can right-click a workspace and choose Reassign to to make a teammate responsible for it.

Will I get my money back? The announcement says active subscribers get a refund, and Pro features are free for existing Pro users from November 4. For the details of your account, email support@conductor.build.

FAQ

Is Conductor shutting down completely? Not yet. Conductor Cloud shuts down on November 20, 2026. The local Mac app keeps working and gets new models and critical fixes until early 2027, when it starts winding down.

Is my code going to be deleted? Your code on GitHub isn’t affected, since Conductor’s cloud workspaces worked on your GitHub repositories. What gets deleted is what’s stored only on Conductor’s servers, such as cloud chat history and workspace state. Push your branches and export your data before November 13.

Does Conductor train on my data? The announcement says Conductor has “never sold or trained on Conductor user data” and still won’t.

Who bought Conductor? Meta. TechCrunch reported that Meta confirmed the acquisition but didn’t share deal terms. On X, Holtz said he was looking forward to working with Meta’s chief AI officer Alexandr Wang and Nat Friedman.

What is Meta going to build with it? Conductor won’t say yet. The announcement only says, “If you liked Conductor, you’re gonna like what’s next.”