Meta acquires Conductor as cloud users face November shutdown deadlines

Conductor announced on November 4 that it is joining Meta, with a transition that puts immediate deadlines in front of its cloud customers. Conductor Cloud becomes read-only on November 13 and closes on November 20, when deletion of cloud user data begins. Company announcement and timeline
Meta confirmed the acquisition to TechCrunch on November 4. Independent confirmation Axios reported that financial terms were undisclosed. Acquisition reporting
For developers, the immediate issue is preserving active work. The announcement offers a route to local workspaces, but a successful migration requires checking what has actually arrived before the cloud service disappears.
An interface for parallel coding agents
Conductor’s documentation describes support for running Claude Code, Codex, Cursor and OpenCode in parallel. Each task receives an isolated workspace with its own branch, files, terminal and review path. The interface also supports reviewing changes, opening pull requests and merging completed work. Conductor product documentation
That places the product around the working process rather than only the model response. Parallel agents can produce more changes at once, but people still need to understand which branch contains which change, which tests passed and what is ready to merge. Preserving that context is an important part of moving a coding workflow.
The acquisition also creates a product question for existing users: how much of that workflow will survive in the next interface? The current announcement does not describe a replacement in enough detail to answer it.
Two cloud deadlines, then a local transition
The read-only period permits reading old chats and exporting data, but prevents new messages. Users should export before November 20. Conductor directs customers to right-click a cloud workspace and choose Transfer to local to move it and its chats to a Mac. A complete data archive is available through Settings, Account, then Export data. Transition instructions
The first check after transfer should be whether the expected workspace and conversation history are present. Teams should also review their repository state, unfinished changes, test results and any work that has not reached a shared remote. An export file and a functioning development environment serve different purposes; having one does not demonstrate that the other is ready.
Local updates end in early 2027 as wind-down starts. Active subscribers receive refunds; existing pro features remain free. Sign-ups and downloads ended November 4. Support and subscription changes
The next product is still a plan
Conductor says it hopes to offer something new in early 2027, without detailing the product. Company’s stated plans That leaves customers with a concrete migration schedule and an incomplete replacement roadmap.
For organizations that depend on agent-based development, this is a useful moment to distinguish portable project assets from service-specific conveniences. Code in a repository, review history, task instructions and workspace configuration may need different preservation steps. A documented owner for each active project can make the transition less fragile.
The acquisition’s longer-term value will depend on what Meta and the Conductor team deliver. Existing cloud customers have a nearer-term priority: move the work, verify the result and finish the export before deletion begins.
Sources and citations
Revision history
Published .