Conductor announced on November 4, 2026 that it is joining Meta. For developers using its coding-agent workspace, the immediate news is a service transition with specific dates, rather than a new product they can adopt today.
The announced timetable
The company’s announcement says new sign-ups and app downloads have stopped. Existing free users cannot upgrade, while existing Pro users can continue using Pro features without paying. Active subscribers will receive a refund.
Conductor Cloud becomes read-only on November 13. Users will still be able to read chats and export data, but will no longer be able to send new messages. The cloud service shuts down on November 20, when deletion of cloud user data begins.
The local application has a longer runway. Conductor says it will receive new models and critical fixes until early 2027. The team expects to have something new available around then, but has not disclosed enough to establish the replacement’s features, availability, or migration contract.
How the documented transfer works
The version 0.93.0 changelog documents two different preservation routes. A cloud workspace and its chats can be moved to a Mac by right-clicking the workspace and selecting Transfer to local. An archive of account data can be downloaded through Settings, Account, then Export data.
Those routes answer different needs. A local workspace supports continuation in the existing local application. An export provides an independent copy that a team can retain and inspect. Neither should be assumed to restore every workflow automatically in an unrelated coding product.
What teams should preserve
Our operational analysis is to check the actual handoff state rather than treating an export button as the end of migration. Identify repositories, branches, uncommitted modifications, task instructions, and decisions recorded only in chat. Verify that the intended remote has the code that teammates need and that a fresh checkout can reproduce the relevant work.
For an unfinished assignment, write a short handoff describing the goal, current changes, remaining decisions, and verification already performed. Keep credentials out of that note. Exported conversations may contain confidential source excerpts or operational details, so they should receive the same access controls as the work they describe.
Test the local transfer while the cloud service is still writable. Open representative files and chats, confirm the correct repository and branch, and check how any necessary environment is recreated. A migration discovered to be incomplete before November 13 leaves more options than one discovered after deletion begins.
A change with practical consequences
The announcement illustrates why a coding workspace is more than its underlying model. It holds context, work in progress, and the interface through which a developer supervises changes. Preserving those assets is the immediate priority. The future Meta product can be evaluated when its actual capabilities and terms are published.