Meta Acquires Conductor, Which Is Shutting Down Its Cloud

By Marcus Bennett

Conductor, an AI coding startup acquired by Meta, will make Conductor Cloud read-only on November 13 and shut the service down on November 20, according to the company's shutdown notice.

The dated sequence gives current cloud users seven days between read-only mode and full shutdown. Conductor says they can preserve workspaces and chats by moving them to a Mac, or download their data through the account settings.

Meta's acquisition does not guarantee continuity of the hosted product. Conductor's shutdown schedule, rather than the deal announcement, defines what customers receive in the short term: a transfer route to local software and a support window for the transition.

What is the timeline?

Conductor's announcements establish five milestones:

• July 2025: Conductor launched with a product for running teams of coding agents.
• November 13: Conductor Cloud becomes read-only.
• November 20: Conductor Cloud shuts down.
• Early next year: Founder Charlie Holtz expects to release a new interface.
• Early 2027: Local Conductor is scheduled to continue receiving new models and critical bug fixes until then.

What changes for Conductor users?

Conductor's official announcement states that existing operations will wind down over the next weeks and months. It also asks users to contact its support team if they need assistance.

Founder Charlie Holtz said Conductor would keep working normally until the planned new interface arrives, with one exception: Conductor Cloud will shut down over the next few weeks.

Conductor Cloud becomes read-only on November 13 and shuts down on November 20. Local Conductor remains in service and continues receiving new models and critical bug fixes through early 2027.

The split matters because Meta's acquisition of the company does not reverse the cloud schedule. Local Conductor has a longer runway, although Conductor gives no exact final day for local support.

What did Meta acquire?

Conductor was one of many AI coding startups. Its product let developers run teams of coding agents—AI systems that carry out coding tasks—from a computer, a mobile device, or the cloud.

The service addressed developers seeking a way to run multiple coding agents. Its three access modes also created separate continuity questions when Meta acquired the company.

Conductor's announcement does not explain whether mobile-device access continues after Conductor Cloud closes. Cloud users have an explicit migration path, while local users can keep the product running.

Holtz wrote: “We launched Conductor a lifetime ago, in the distant past of July 2025. Writing most of your code with agents (let alone a team of coding agents) felt crazy back then. You trusted us to come along for the ride, and we cannot thank you enough!”

The July 2025 launch date gives the company a short public history before the acquisition. Holtz's account places a product built around agent-assisted coding on a path from an implausible use case to ownership by Meta.

The transaction adds Meta to a field of AI coding startups built around agent teams. Conductor's materials present the deal as an acquisition of the company, but they do not describe a post-acquisition operating structure.

For developers, the operating stakes are immediate because Conductor's product included cloud workspaces and chats. For Meta, the strategic payoff remains unspecified because the announcement names no internal product, integration plan, or commercial arrangement.

Conductor's public materials do not show whether its product or team will join a Meta developer platform, support Meta's own coding systems, or remain a separate service. The evidence supports only the acquisition and the transition schedule.

What comes in the next interface?

Holtz also wrote: “We have some big, crazy plans for the next interface. If you liked Conductor, you’re gonna love what’s coming. We’ll have something new for you to use early next year.”

Early next year is the only release window. Conductor's announcement does not name the successor, identify any models, publish benchmarks, state pricing, or say whether Conductor Cloud will return.

Local Conductor's continued updates through early 2027 overlap with the promised new interface. Conductor does not clarify whether that interface is a rebuilt local product, a separate application, or another delivery method.

Conductor's public materials provide no benchmark or model list with either the acquisition or shutdown notice. That omission prevents customers from comparing Conductor's model performance, update quality, or operating cost with alternatives.

How do users migrate their data?

Conductor's shutdown instructions give cloud customers two documented routes. To move a workspace and its chats to a Mac, users can right-click the workspace and choose Transfer to local. For a broader download, the company directs them to Settings → Account → Export data.

These actions cover different needs. Transfer to local moves a workspace and its chats onto a Mac. Export data provides a way to download all available account data. Conductor does not specify file formats, export size, retention periods, or whether the two processes produce identical records.

Users who need migration help can email [email protected]. Conductor says its support team will assist with the transition, although it provides no response-time target, phone channel, or dedicated transition period beyond the general wind-down window.

November 13 is the first hard operational deadline. After that date, cloud workspaces are designated read-only; November 20 is the endpoint for the hosted service. Local Conductor has no matching shutdown date and remains supported through early 2027.

The shutdown affects one of Conductor's three original delivery modes. Computer-based local use continues, but Conductor leaves mobile continuity unclear and ends cloud access on a fixed schedule. That asymmetry gives existing customers unequal transition windows.

What has the acquisition not disclosed?

Conductor's acquisition announcement discloses no purchase price, consideration structure, funding history, employee count, or employees' roles. It also contains no statement from a named Meta executive.

For an AI coding acquisition, those omissions limit outside assessment of scale and strategic value. Conductor's materials provide a launch date, transition dates, and product commitments, but no revenue, user, benchmark, or model data.

Evaluation is equally constrained. A product promising new models cannot be judged on model identity or test performance until those details appear, and Conductor's source provides no independent benchmark to fill the gap.

What should users watch next?

For current customers, the nearer test is operational: anyone retaining cloud workspaces or chats needs to transfer or export them before November 20, while local users can continue receiving critical fixes until early 2027.

The next public milestone is the new interface Holtz placed in early next year. Without a firmer date, feature list, model roster, or pricing, developers cannot yet determine whether it preserves the team-agent workflow central to Conductor.

Meta has acquired a July 2025 AI coding startup whose cloud tier shuts down on November 20 while local software receives updates into early 2027. The strategic payoff stays unstated until the company reveals what the next interface actually does.