Latest in AI
Conductor Joins Meta: Cloud Shutdown Dates and How to Export Your Work
Conductor users have two weeks to move cloud workspaces, while the team prepares a new product for early 2027.
Conductor announced on November 4 that it is joining Meta. For developers using its coding-agent interface, the immediate change is a migration deadline: Conductor Cloud becomes read-only on November 13 and shuts down on November 20. Local users have more time, but the current product is also heading toward a wind-down.
Conductor Cloud shutdown dates
The official announcement sets out this schedule:
- November 4: new sign-ups and app downloads stop. Existing Pro users retain their features free; free users cannot upgrade.
- November 13: cloud workspaces become read-only. Chats remain readable and exportable. Active subscribers receive refunds.
- November 20: Conductor Cloud closes and cloud user-data deletion begins.
- Early 2027: local Conductor starts winding down. Until then, it will receive new models and critical bug fixes.
The team expects to offer something new early next year, but has not described the product. A future replacement is not a migration plan for work that needs to continue this month.
How to export Conductor workspaces
To move a cloud workspace and its chats to a Mac, right-click the workspace and select Transfer to local. To download an archive of all Conductor data, use Settings, then Account, then Export data.
Do this before the cloud deletion deadline. An export is also worth opening and checking while the original service remains available. A backup that has not been inspected leaves the same uncomfortable question until migration day: did it preserve the information you actually need?
For a team, I would start by separating code from the context around it. A repository may contain the finished changes while the agent conversation explains rejected approaches, unfinished work and decisions that never became a commit. Check both rather than assuming a source-code backup captures the whole workspace.
What Meta gets, and what users still need
TechCrunch reports the acquisition. The announcement itself leaves the next interface largely unspecified.
The Hacker News discussion includes both congratulations and frustration from people who relied on Conductor's workflow. Those comments are individual reactions, but they point to a practical issue with adopting an agent interface: the tool accumulates working context as well as generating code.
That makes export quality part of the product decision. When evaluating a replacement, try one real workspace and check how its conversations, files and unfinished tasks carry over. A polished new interface matters less if every transition requires reconstructing why the previous agent made its choices.
I’m Paras. I work at the intersection of AI, engineering and distribution.
I help technical founders turn product changes and launch decisions into clear stories developers can use and share.