Quick Answer
Meta has acquired Conductor, and Conductor Cloud will shut down on November 20, 2026. The AI coding service has already stopped new sign-ups and downloads, while cloud workspaces become read-only on November 13. Export or transfer cloud data before November 20. Existing Pro users keep Pro features free during the transition, and active subscribers are promised refunds.
Key Takeaways
- Meta acquired Conductor, although the companies have not disclosed deal terms.
- Conductor stopped new user registrations and app downloads on November 4, 2026.
- Conductor Cloud workspaces become read-only on November 13, 2026.
- Conductor Cloud shuts down and begins deleting user data on November 20, 2026.
- Users can export cloud data or transfer a workspace to a Mac before the shutdown.
What did Meta acquire from Conductor?
Meta acquired Conductor, an AI coding product designed to help developers coordinate multiple AI coding agents in parallel. Conductor announced on November 4, 2026, that it is joining Meta, while the acquisition itself was separately confirmed by Axios. Deal terms were not disclosed.
The Meta Conductor acquisition matters because Conductor focused on a developer workflow rather than a general-purpose chatbot experience. The product enabled developers to work with multiple coding agents in parallel, which can be useful when a project needs separate tasks handled at the same time. The acquisition does not yet establish which Conductor features, if any, Meta will incorporate into future products.
Meta has not announced a replacement cloud product for Conductor users. Developers who depend on coordinated AI coding workflows should therefore treat the Conductor Cloud closure as an immediate migration issue, not as a promise that Meta will automatically preserve the same service. Developers evaluating other assisted development methods may also want to understand the operational limits of vibe coding before moving important work into a new tool.
What changes for Conductor Cloud users now?
Conductor Cloud users can no longer create new accounts or download the app, because Conductor stopped new user sign-ups and downloads on November 4, 2026. Existing free users cannot upgrade to Pro, while existing Pro users retain their Pro features free of charge during the transition.
Conductor Cloud subscribers should not assume that continued access means the cloud service will remain available. The company has set a sequence of closure dates that progressively reduces what users can do with a cloud workspace. The practical response is to identify any chats, project context, or workspace data that needs to remain accessible after the shutdown.
Active Conductor Cloud subscribers are promised refunds. Conductor has not provided further refund details in the announcement materials cited for this article, so subscribers should monitor their account communications and retain billing records until the refund is complete. Users who need account-specific help should contact Conductor before the November 20 shutdown date.
When does Conductor Cloud become read-only and shut down?
Conductor Cloud workspaces become read-only on November 13, 2026, and Conductor Cloud shuts down on November 20, 2026. Conductor says users can still view chats and export data after the read-only change, but they cannot send new messages from a cloud workspace.
| Date | Conductor Cloud change | What users should do |
|---|---|---|
| November 4, 2026 | New sign-ups and app downloads stop. | Existing users should review whether their cloud workspace contains data they need to keep. |
| November 13, 2026 | Cloud workspaces become read-only. | Export chats and data before the workspace can no longer accept new messages. |
| November 20, 2026 | Conductor Cloud shuts down and data deletion begins. | Complete exports or a Mac transfer before this date. |
Conductor’s published timeline makes November 20 the important deadline for users with data stored in the service. A read-only workspace can still be useful for checking prior chats, but it cannot support ongoing work after November 13. The safest approach is to finish migration before the read-only date, rather than waiting until the final shutdown window.
The shutdown schedule is set out in Conductor’s acquisition announcement. The company says it will begin deleting cloud user data after the cloud service closes, which means an account login alone is not a sufficient backup plan.
How can Conductor users export or transfer workspace data?
Conductor users can transfer a cloud workspace to a Mac or export all account data before Conductor Cloud closes. Conductor says users can right-click a cloud workspace and choose “Transfer to local” to move that workspace to a Mac.
Conductor users can also export account data through Settings > Account > Export data. An export is the better choice for users who want a separate copy of their cloud information, while a local transfer is intended for users who want to continue working from a Mac-based workspace. Users should verify that exported files are saved in a location they control.
- Open the Conductor cloud workspace you want to preserve.
- Right-click the workspace and select Transfer to local if you use a Mac.
- Open Settings > Account > Export data if you need an account-wide export.
- Save the exported data to local storage you can access after November 20.
- Confirm that the transferred workspace or exported files contain the chats and information you need.
Conductor data should be checked before the shutdown because the company will begin deleting cloud user data after November 20. Stop and contact Conductor support if a transfer or export fails, particularly if the workspace contains project material that cannot be recreated. Do not delete local copies until you have confirmed that the transfer or export is complete.
Will local Conductor continue to work after the cloud shutdown?
Local Conductor will continue receiving new models and critical bug fixes until early 2027, when the local product begins winding down. Conductor has not provided a more specific end date in its November 4 announcement, so local availability should be treated as temporary rather than permanent.
Local Conductor gives Mac users a path away from the closing cloud service, but it does not remove the need for a longer-term plan. New models and critical bug fixes can keep the software useful during the transition, yet a winding-down product may not receive the same level of future support as an actively expanding platform.
The practical response is to use the local period to preserve work and assess alternative workflows. Developers who rely on editing files inside an AI conversation may also compare tools that offer in-chat document and code editing, although a feature comparison should include data controls, export options, and the ability to retain project context.
Why does the Meta Conductor acquisition matter for developers?
The Meta Conductor acquisition gives Meta a team and product experience centered on coordinating multiple AI coding agents. Meta has not detailed its product plans, but a Meta spokesperson said the acquisition will strengthen the company’s developer-focused AI capabilities, as reported by The Register.
Multiple-agent coding systems matter because developers may use separate AI agents for different parts of a software task. One agent could address a coding problem while another examines related work, although the researched materials do not specify Conductor’s individual agent roles or technical architecture. The main confirmed point is that Conductor was built to coordinate multiple coding agents in parallel.
Meta’s statement should be read as an intention rather than a confirmed feature roadmap. The acquisition does not establish that Conductor Cloud will be revived, that local Conductor will remain available beyond its stated wind-down, or that every Conductor capability will appear in Meta products. Developers should make migration decisions based on the published shutdown schedule, not on possible future integrations.
What should Conductor subscribers and teams do before November 20?
Conductor subscribers and teams should export or transfer cloud workspace data before November 20, 2026, because Conductor will then shut down the cloud service and begin deleting cloud user data. Teams should make the deadline visible to anyone who owns projects, chats, or billing access in the account.
Conductor teams should also separate two tasks: preserving information and selecting a replacement workflow. Data preservation has a firm deadline, while choosing a future AI coding platform requires more time to evaluate privacy practices, model access, collaboration features, and export controls. The closure does not require teams to select a replacement immediately, but it does require teams to retain the information needed to make that decision.
- Export all data through Settings > Account > Export data.
- Transfer active cloud workspaces to local storage on a Mac where appropriate.
- Verify that important chats and project information appear in the local or exported copy.
- Review refund communications if the account has an active Conductor Cloud subscription.
- Choose a future workflow after the data preservation work is complete.
Conductor users should avoid treating a cloud chat history as the only record of important development decisions. A separate local copy gives a team a way to review prior context after the cloud service is gone. The most sensible approach is to complete the export before November 13, when cloud workspaces lose the ability to send new messages.
FAQ
Did Meta acquire Conductor?
Yes, Meta acquired Conductor, and Conductor announced on November 4, 2026, that it is joining Meta. The companies have not disclosed deal terms.
When will Conductor Cloud shut down?
Conductor Cloud will shut down on November 20, 2026. Conductor says it will begin deleting cloud user data after the shutdown, so users should export or transfer data first.
Can Conductor users still send messages after November 13?
No, Conductor Cloud workspaces become read-only on November 13, 2026. Users can view chats and export data, but they cannot send new messages from those workspaces.
How can Conductor users save their data?
Conductor users can export data through Settings > Account > Export data or transfer a cloud workspace to a Mac through the “Transfer to local” option. Users should confirm that the local or exported copy contains necessary project information before November 20.
Will local Conductor continue after Conductor Cloud closes?
Local Conductor will receive new models and critical bug fixes until early 2027, when it begins winding down. Conductor has not announced a specific final end date for the local product.