Meta buys Conductor: Nov 20 cloud shutdown leaves coding-agent teams a migration deadline
The multi-agent coding startup is joining Meta. Existing users face a more immediate issue: protecting their cloud workspaces, conversations and project context.
Conductor confirms that it is joining Meta, with sign-ups ending November 4, cloud workspaces going read-only November 13, and cloud shutdown plus the start of cloud-data deletion on November 20. Users should export and independently check their work rather than assume a future Meta interface preserves it.
Sources and limitations
- Primary / confirmation source
- Primary / confirmation source
- Primary / confirmation source
- Editorial analysis, not a product test
Vendor-reported shutdown and export terms, with independent press confirmation of the acquisition. No hands-on verification of workspace transfer, deletion procedures, licensing or Meta's next product.
1. The deal is real; the next product is still a promise
On November 4, 2026, Conductor founder Charlie Holtz announced that the company is joining Meta. Conductor says it hopes to offer a new interface in early 2027, but the original announcement does not promise specific integrations, a price, model choice, enterprise policies or a precise shipping date.
Conductor coordinates multiple AI coding agents working on isolated project workspaces. Its value lies in parallel work and review rather than a single proprietary model. The near-term operational reality, however, is a sunset of the existing hosted service. The acquisition is confirmed; the properties of an eventual Meta successor are not.
2. Four milestones: November 13 and November 20 are not interchangeable
The company's official timeline separates registration, cloud availability and the local application's support period:
| Date | Officially described change | Operational response |
|---|---|---|
| Nov 4 | No new sign-ups or downloads; paid features temporarily remain free for existing Pro users. | Inventory existing accounts and subscriptions. |
| Nov 13 | Conductor Cloud becomes read-only; existing chats can be read and data exported, but no new messages. | Finish active cloud work in advance. |
| Nov 20 | Conductor Cloud closes and cloud-user-data deletion begins. | Export, validate and safeguard project data before shutdown. |
| Early 2027 | Local Conductor receives new models and critical fixes until the wind-down period. | Plan for a limited transition, not perpetual support. |
The wording matters: beginning cloud-data deletion on November 20 is not proof that every related record has already been deleted that day. Nor does the continued local app mean the cloud service remains available.
3. How to export Conductor Cloud workspaces and chat history
Conductor describes two actions. To move an individual cloud workspace and associated chats onto a Mac, right-click the workspace and choose Transfer to local. To export a broader archive, open Settings → Account → Export data. The procedure is documented in the company FAQ.
AgentenCode recommendation: treat an export as a claim to test. Reopen a sample project locally, verify source files and Git branches, locate the expected conversations, and reconcile relevant decisions, pull requests and dependencies. Check whether credentials, external tool connections, or remote artifacts require separate action. These are quality-control questions; we do not claim that every data category is guaranteed in the exported archive.
Preserve a second access-controlled copy and record the accountable owner of the migration. For business-critical repositories, keep Git history and release decisions independently accessible.
4,.,
<,p,>5. Meta's opportunity is the orchestration layer
Our inference: Meta appears interested in developer interfaces that coordinate coding agents, potentially including those supplied by different model providers. That is strategically different from simply releasing another coding model. But the announcement contains no verified guarantee that a 2027 product will preserve Conductor's current model-agnostic behavior or subscription terms.
OpenAI announced a plan to acquire Pierre Computer in the same week. The comparison illustrates two layers of the evolving software stack: Pierre focuses on diffs, navigation and code storage; Conductor's heritage is parallel-agent orchestration. It is too early to designate a winner or infer an integration roadmap.
6. Data protection, permissions and support are separate questions
Conductor states it has not sold customer data or used it to train models and does not intend to do so. Those are vendor statements, not independent privacy audit results. Administrators must still examine their own export, retention, secrets, access controls and affected vendor agreements.
Running the local application can reduce dependence on Conductor Cloud, but it cannot guarantee future model compatibility or security updates beyond the published support period. A forthcoming Meta service might change those conditions; its policies are not yet established. AgentenTrust documents the difference between sourced controls and unknown claims.
7. AgentenCode decision matrix: confirmed, supported, or unknown?
This original matrix separates documented deadlines from assumptions about a future platform:
| Question | Evidence on Nov 5 | Decision |
|---|---|---|
| Cloud read-only on Nov 13 | Officially confirmed | No new hosted tasks after that date. |
| Cloud shuts Nov 20; deletion begins | Officially confirmed | Export and verify before shutdown. |
| Local app updates until early 2027 | Time-limited vendor statement | Treat as a migration bridge. |
| Future Meta interface | Announced intent, details unavailable | Do not budget unannounced features or prices. |
| Complete restoration of every workflow | Not independently tested | Perform customer-specific recovery checks. |
AgentenCode analysis: the decisive measure is not simply whether an archive exists, but whether a team can resume authorized work without the retiring cloud service. That requires an actual project-specific test.
8. Three actions before the deadline
Today: identify workspace owners, export data, and preserve independent source-control history. Before November 13: complete active cloud sessions, test local transfers and record outstanding pull requests and agent decisions. Before November 20: verify the archive, secure it, and document a restore rehearsal.
Teams can monitor Meta's planned interface for early 2027, but should not base production continuity on an unspecified future product. This story is both a strategic signal for coding agents and a practical migration deadline.
FAQ
Is Conductor Cloud already offline?
No. As of Nov 5, Conductor says it will be read-only November 13 and shut down November 20, when cloud-data deletion starts.
How do I export Conductor workspaces?
Use Transfer to local from a cloud workspace's context menu, or Settings → Account → Export data for an archive.
Will the local Conductor app still work?
The company plans new models and critical bug fixes through early 2027, followed by a wind-down. That is not a perpetual support guarantee.
Has Meta announced the replacement product?
Only a prospective new interface for early 2027. Features, pricing and migration compatibility have not been established.
Did AgentenCode independently test the export?
No. The procedure is vendor-documented, and teams should perform their own recovery verification.
Methodology, original sources and transparency
We reviewed Conductor's original November 4 announcement and 0.93.0 changelog, alongside press confirmation of the acquisition. No product, customer export, actual deletion process or planned Meta service was independently tested. The migration matrix and operational suggestions are AgentenCode's own editorial analysis.
Original sources: Conductor primary announcement, Nov 4 · Conductor 0.93.0 changelog, Nov 4 · TechCrunch: Meta confirms acquisition, Nov 4