What happened
Conductor’s announcement says the company is joining Meta. It describes the product as having launched in July 2025, when the founders say writing most code with agents—or coordinating a team of coding agents—still felt unusual. The company says it has plans for a “next interface” and hopes to have something new for users early next year, but gives no further product details.
The transition affects sign-ups and plans immediately. As of Wednesday, Nov. 4, new users can no longer sign up for Conductor or download the app. Existing free users cannot upgrade to a Pro plan. Users who already have Pro can continue using Pro features for free. Conductor says local use will continue for now, with new models and critical bug fixes through early 2027.
Conductor Cloud has a separate shutdown schedule. On Friday, Nov. 13, cloud workspaces become read-only: users can still read old chats and export data, but cannot send new messages. On Friday, Nov. 20, Conductor says it will begin deleting cloud user data. Users can move a cloud workspace and its chats to their Mac by right-clicking the workspace and choosing “Transfer to local.” To download a full data archive, the instructions are Settings → Account → Export data. The company asks users to export before Nov. 20.
Active subscribers will receive a refund, according to the announcement. The company says it has never sold or trained on Conductor user data and will not do so; it says all Conductor user data will be deleted when the app shuts down in early 2027. The announcement does not specify a price, refund processing timetable, or what the replacement interface will contain. It says only that Conductor hopes to have something new for users early next year.
What the archive adds
The archive has already covered Meta’s acquisition of Conductor and the Conductor Cloud shutdown, stating that the cloud service would shut down Nov. 20. This announcement supplies the underlying user-facing timetable and migration instructions: read-only access begins Nov. 13, and users can transfer workspaces to local or export an archive. It is additional detail on a known story, not a new acquisition.
Trend signal
This supports the pattern that harness architecture outlives model choice, though only provisionally: Conductor says local use will receive new models and critical fixes through early 2027 while it transitions toward a new interface. The announcement does not establish whether that future interface will preserve the same harness or become a distinct product.
Why now
The acquisition announcement comes with near-term service changes, not just a future product promise. New sign-ups have stopped, cloud workspaces become read-only Nov. 13, and deletion begins Nov. 20. Those dates make exporting or transferring data time-sensitive for current users.
Connections to other events
A Nov. 4, 2025 Telegram post described Conductor as a native Mac app for running multiple Claude Code agents in isolated repository copies, comparing diffs, and merging changes. The current announcement concerns the same product, but adds a corporate transition and a wind-down plan for its cloud service. It does not say whether the future Meta interface will retain that workflow.
Why it matters
For teams using Conductor Cloud, the acquisition is an operational migration event. The hard deadline is not the promised interface early next year; it is the loss of write access on Nov. 13 and the start of data deletion on Nov. 20. Teams should identify cloud workspaces, transfer the ones they need to local Mac installations, and export a full archive before deletion begins.
The announcement also separates the product’s local and cloud futures. Local Conductor is not ending immediately: it is expected to receive new models and critical fixes until early 2027. But the company has not promised a longer-term support path, nor explained how the planned Meta product will relate to local workspaces. Teams therefore should treat the near-term migration as necessary while avoiding assumptions that existing workflows will carry over unchanged. Earlier coverage: Meta acquires Conductor, the startup for running multiple AI coding agents in parallel; Conductor Cloud to shut down Nov 20.
What happens next
- Conductor Cloud workspaces become read-only on schedule. (3 months, 95%). Watch for: access changing on Nov. 13 as announced.
- Conductor begins deleting cloud user data on schedule. (3 months, 90%). Watch for: the Nov. 20 shutdown and deletion notice.
Limits and uncertainty
The announcement does not explain the terms of the acquisition, the scope of Meta’s involvement, or what the “next interface” will do. It gives no details about how many users or workspaces are affected, how refunds will be processed, or whether a local workspace can later be imported into a successor product. The company says it has not sold or trained on user data and plans deletion at app shutdown, but the announcement alone does not independently verify those data-handling claims. The specific dates and instructions here are those stated in the source.
Skill to build now
This week, inventory any Conductor Cloud workspaces your team still needs. For each, use “Transfer to local” on the workspace menu, then create a full archive through Settings → Account → Export data. Confirm that the transferred chats and exported archive are readable before the Nov. 20 deletion begins; do not rely on a cloud workspace remaining writable after Nov. 13.
Reader takeaway
Meta’s acquisition is less urgent to act on than Conductor Cloud’s shutdown calendar. Move the workspaces you need to local and export your data before Nov. 20; Conductor says the local app continues for now, but its longer-term replacement remains unspecified.