Following Meta’s acquisition of Conductor, existing cloud workspaces will shut down. That adds a testable condition to the idea that switching models preserves a workflow: can a colleague continue an unfinished task after its workspace moves to a local machine? If the execution environment or review context needs rebuilding, having more models to choose from has not removed that migration cost. Announcement Cloud architecture
The announcement starts its transition timeline on 2026-11-04, without a publication time or timezone. Axios independently reported the acquisition. This article is dated 2026-11-05 in Taipei, with an 08:37 research cutoff; an American calendar date is not treated as an exact event time in Taipei. Timeline Independent reporting
Conductor runs Claude Code, Codex, Cursor and OpenCode in parallel, then helps people review and merge their changes. Tasks have separate workspaces and branches. This provides an interface for deciding which changes belong in a repository after an agent produces them. Product mechanism
In its March 30 fundraising post, the company said businesses including Google and Meta each had dozens of engineers using the product. That is vendor-reported adoption, not proof of enterprise contracts or reduced working hours. The acquisition announcement does not disclose the number of active cloud customers affected, so the overall migration burden cannot be quantified. Historical adoption Announcement scope
Cloud service ends before the new interface arrives
From November 4, Conductor stops new registrations and downloads; existing Pro users retain Pro features for free. Cloud workspaces become read-only on November 13, with refunds for active subscribers. Shutdown and the start of cloud-data deletion follow on November 20. November 4 and November 20 are 16 calendar days apart, not a guarantee of an exact number of remaining service hours. Access changes
The company offers transfer of workspaces and chats to a Mac, plus a full data export. Local Conductor receives new models and critical fixes until early 2027, when it too starts winding down. The team hopes to offer a new product then, but has not specified its full capabilities or a firm launch date. Transfer and maintenance Future plans
The environment changes matter. Cloud agents run in isolated Linux sandboxes, with shared workspaces and conversations; they can continue after a laptop closes until the sandbox sleeps. Local work runs on the user’s Mac. Moving the data does not establish that shared access and continued execution have also been preserved. Environment differences
I see value in bringing multiple agents’ output into one review process. Engineers need to decide whether to accept a change; they do not necessarily want to manage each tool’s interaction patterns separately. But that value depends on understandable differences and task states. Merely starting more agents does not demonstrate faster delivery. The acquisition brings experience designing this interface; the performance of a future integrated product remains unproven.
Consider a hypothetical engineer who assigns debugging to an agent, with a colleague taking over the following day. Code alone may not explain why an earlier modification was rejected. A chat archive without an environment that can rerun the tests may still require reconstruction. This example shows how preservation requirements depend on the successor’s task; it is not a documented incident affecting these users.
For a team already using Conductor Cloud, I would preserve unmerged work and the reasoning behind it before choosing the next interface. Meta’s subsequent product could create useful integration if it makes agent changes easier to review. That expectation should be reduced if users repeatedly have to reconstruct task context. The observable outcome is how much information a colleague must request, and how many steps must be repeated, when taking over comparable work—not how many models appear in a menu.
The event image could not be downloaded because the download environment could not resolve its domain. The cover reuses this site’s historical Meta coding-agent image; it does not depict Conductor’s new interface.
Sources: