What happened
In its version 0.93.0 changelog, dated November 4, 2026, Conductor announced that it is joining Meta. The post points readers to an announcement but, in the supplied changelog text, gives no terms of the acquisition, financial details, or explanation of how the product or team will be integrated. Its immediate practical focus is the product transition: Conductor says it will wind down the service over the coming weeks and months.
The timeline is specific for Conductor Cloud. It will go read-only on November 13 and shut down on November 20. The changelog describes how to move a cloud workspace and its chats to a Mac: right-click the workspace and choose “Transfer to local.” Users who want a broader copy of their information can go to Settings → Account → Export data and download all their data. The source does not describe the export format or say how long exports will remain available, so users should not assume they can retrieve material after the service closes.
The local Conductor application is not given the same shutdown date. Instead, the company says local Conductor will continue to get new models and critical bug fixes until early 2027. That statement establishes a support window, but does not promise continued development or support after that point. The changelog does not say whether features that depend on Conductor Cloud will work locally, or whether workspaces transferred to a Mac retain every cloud-specific property.
Version 0.93.0 also includes smaller product changes and fixes. Users can set custom completion sounds in Settings → General by choosing and naming a sound file. Archived cloud workspaces show their pull requests, last known changes, and file tree in a right panel. The Codex model picker adds GPT-6.1 Terra. The release fixes the Claude account usage display when Claude Code reports newer limit data, as well as several interface issues involving chat history, agent-to-agent messages, workspace renaming, pull request titles, and expanded Mermaid diagrams. These changes are listed alongside the wind-down notice; the source does not say they alter the shutdown plan.
What the archive adds
This is a follow-up detail on an already covered event, not a new acquisition. Our November 4 Field Note recorded the acquisition and the November 20 Conductor Cloud shutdown. A second archive note identifies the same event. This changelog adds the November 13 read-only date, transfer and export instructions, and the stated support window for local Conductor.
Trend signal
This update is not enough to support or weaken a broader SITE_PATTERNS thesis. It documents a vendor transition and offers a migration route for one product, but supplies no evidence about the wider economics of agents, their architectures, or interoperability practices.
Why now
The product transition is imminent: the changelog was dated November 4, while Conductor Cloud is scheduled to become read-only on November 13 and close on November 20. The source does not explain the timing beyond saying Conductor is joining Meta and that the service will be wound down over the coming weeks and months.
Connections to other events
A prior Telegram post in the archive said Manus had officially joined Meta while its product and subscription remained in place. That earlier announcement described continuity; Conductor's changelog instead specifies a cloud shutdown and a limited support horizon for its local app. The two cases show different transition plans, not evidence of a common Meta policy.
Why it matters
For a team using Conductor Cloud, the important decision is operational rather than strategic: identify which workspaces and conversations must survive, then move or export them before access changes. The read-only date precedes the shutdown by a week, so it is not a safe substitute for a migration plan. Teams should also distinguish the cloud closure from local-app support: local Conductor is promised new models and critical fixes only until early 2027, with no longer-term commitment stated here.
The changelog supplies a transfer path and an all-data export setting, which makes immediate preservation possible without guessing at a migration procedure. But it does not confirm that all cloud state maps cleanly to the local app, or explain the future of cloud-dependent workflows. Builders should inventory the specific artifacts and routines they rely on, test that transferred workspaces contain what they need, and avoid treating continued local updates as a guarantee that the product will remain a supported long-term dependency.
Limits and uncertainty
The supplied changelog does not provide the acquisition terms, the reason for the shutdown, or details of Conductor's future inside Meta. It does not specify the export format, whether exported data includes every type of account or workspace information, or whether the export function will remain available after November 20. It also does not explain what happens to cloud-dependent capabilities after transfer, or define “early 2027” more precisely. The support statement is limited to new models and critical bug fixes for local Conductor; it is not a promise about support beyond that period.
Skill to build now
This week, make a small migration checklist for any Conductor Cloud workspace your team depends on. Record the workspace owner and critical chats, transfer a representative workspace to a Mac using the documented right-click menu, and inspect the result for the files and history your workflow needs. Then use Settings → Account → Export data to preserve a complete account export. Keep the exported copy somewhere your team controls, and test that another teammate can locate and use the saved material; the changelog does not describe the export format or guarantee that transferred workspaces preserve every cloud feature.
Reader takeaway
Conductor Cloud has two near-term deadlines: read-only access begins November 13 and shutdown follows on November 20. Transfer important workspaces and chats to a Mac or export account data ahead of those dates. Local Conductor is slated for new models and critical bug fixes until early 2027, but the changelog makes no commitment beyond that window.
Open question
Will Meta maintain or replace the local Conductor product after the stated support window ends in early 2027?