Meta has acquired Conductor, an AI coding tool that lets developers run multiple agents at once. But the deal comes with a deadline for existing users: Conductor Cloud will shut down Nov. 20, 2026, when the company says it will begin deleting cloud data.
The shutdown happens in two stages. Cloud workspaces become read-only Nov. 13, leaving users unable to send new instructions to their agents. Developers can still view conversations and export data until the service closes a week later.
Conductor confirmed the acquisition and shutdown schedule in a Nov. 4 announcement. It has also provided instructions for transferring cloud workspaces to a Mac or downloading an account archive.
When does Conductor Cloud shut down?
Conductor was designed to help developers manage several AI coding agents working on different parts of a project. Rather than developing its own AI models, the platform brings together tools such as Claude Code and OpenAI Codex in separate workspaces.
That approach gives developers a way to coordinate tasks, inspect changes, and manage parallel coding sessions. Other AI coding agents can also handle repository changes and development tasks, although their interfaces and workflows differ.
Conductor’s shutdown schedule is now confirmed:
- Nov. 4: New sign-ups and app downloads stopped. Existing free users can no longer upgrade to Pro, while current Pro users retain their paid features at no charge.
- Nov. 13: Conductor Cloud becomes read-only. Users can still view previous chats and export data, but cannot send new messages.
- Nov. 20: Conductor Cloud shuts down, and deletion of cloud user data begins.
- Early 2027: The local Conductor app begins winding down after receiving new model support and critical bug fixes through that period.
Conductor says active subscribers will receive refunds. It has not published a specific refund amount or processing schedule.
The company also says it has never sold user data or used it to train AI models. It plans to delete remaining Conductor user data when the local app shuts down in early 2027.
How to export Conductor projects and chats
Conductor provides two ways to preserve cloud data before Nov. 20. Users can transfer individual workspaces to their Mac or download an archive of their account information.
To transfer a cloud workspace:
- Open Conductor and locate the cloud workspace.
- Right-click the workspace.
- Select Transfer to local.
- Allow the transfer to finish, then check that the workspace and its chats are accessible on the Mac.
To export account data:
- Open Settings in Conductor.
- Select Account.
- Choose Export data.
- Download and securely store the resulting archive.
These instructions come directly from Conductor’s announcement and accompanying version 0.93.0 release notes.
Although exports remain available during the read-only period, completing them before Nov. 13 gives developers more time to resolve any problems.
Teams should also verify that important code changes are committed and pushed to their Git repositories. Conductor hasn’t specified every file or setting included in its export archive, so developers shouldn’t assume the downloaded data will reproduce an entire working environment.
Anyone using cloud-specific configurations should document the dependencies, environment settings, and credentials needed to recreate their development setup. Secrets should be transferred securely rather than copied into an unprotected archive.
Will Conductor’s local Mac app keep working?
Yes, for now. Conductor says its local application will continue operating and receive new model support and critical bug fixes until early 2027.
The company hasn’t announced an exact shutdown date for the local app or explained which features, if any, might stop working as support winds down.
Developers who move their workspaces to a Mac therefore have more time to transition, but the local app isn’t a permanent replacement for Conductor Cloud.
For those planning a longer-term switch, the choice depends on how they use coding agents. Some developers prefer a dedicated desktop application, while others work directly in a terminal or use agents integrated with their existing editor.
For example, OpenAI’s Codex desktop app supports parallel coding tasks, while other platforms offer different approaches to managing agent workspaces.
Developers should test alternatives against their existing repositories and workflows before retiring Conductor, particularly if they rely on multiple agents working simultaneously.
What Meta plans to do with Conductor
Conductor founder Charlie Holtz announced that the company is joining Meta and said the team is working toward a new interface expected in early 2027.
The announcement doesn’t identify a replacement product, provide pricing, or confirm whether Conductor’s current features will be incorporated into Meta’s existing developer tools.
Meta already has its own AI coding product, Muse Code, but neither company has confirmed that Conductor users will be migrated to it.
The acquisition price also remains undisclosed.
For developers currently using Conductor Cloud, those unanswered questions can wait. The immediate task is to transfer workspaces, export account data, and verify that essential projects remain accessible before Nov. 20.
Also read: Developers preparing to replace Conductor can compare Claude Code alternatives, including Codex, Cursor, GitHub Copilot, and other AI coding tools.