Meta confirmed on November 4 that it acquired Conductor, the startup behind a workspace for running several coding agents at once. For anyone using the product, the date that matters is November 20.
The Conductor cloud shutdown date is November 20
The company's own announcement sets the closure for November 20. After that it starts deleting user cloud data. Local core features keep working until early next year. Anyone with work parked in Conductor's cloud has a little over two weeks to move it.
That deadline is the most useful part of the whole story. Everything else is strategy, and strategy doesn't cost you a Tuesday afternoon.
Two weeks, roughly.
What Conductor AI coding did differently
Conductor was founded in 2024 and launched its core product in summer 2025. The pitch was parallel coding agents: several agents working in separate workspaces at the same time, running on the cloud, on a local machine, or from a phone.
The agents themselves came from outside labs such as Anthropic and OpenAI. Conductor built the workspace around them, which is a different job from training a model. One company supplies the intelligence. The other supplies the desk, the filing system and the switchboard.
In practice that means handing the same task to more than one agent, letting each work in isolation, and comparing what comes back. Isolation is the point. Two agents editing the same file at once produce a mess, and separate workspaces keep their changes from colliding.
What Conductor doesn't do is write the code itself, which is why this acquisition reads as a bet on workflow rather than on model capability.
Why Meta bought a parallel coding agents startup
Meta shipped its own coding agent, Muse Code, in August 2026, and its Muse assistant passed 10 million US downloads. Earlier AI acquisitions include Moltbook.
Conductor adds orchestration. Once you run four agents at once, the hard part stops being generation and becomes review, because four diffs arriving together is harder to read than one. A tool that manages that queue has an obvious buyer inside any lab shipping agents.
So what is Meta actually buying? A workflow its own agent can plug into, and a team that has spent a year thinking about what happens after generation stops being the bottleneck.
Where Conductor lands inside Meta Superintelligence Labs is unclear
Founder and CEO Charlie Holtz wrote that Conductor is joining Meta and teased "something new" for customers by early next year. He said he looks forward to working with Alexandr Wang and Nat Friedman.
Meta confirmed the acquisition to TechCrunch without giving terms. The price stays unknown. Whether the team lands inside Meta Superintelligence Labs hasn't been disclosed either, and neither company has said which group absorbs the product.
Both of those gaps are normal for a deal announced this way. They also decide whether existing users get a migration path or a polite goodbye, and that answer matters more to a team of five than to the acquiring company.
The AI coding tools race Meta just joined
Large labs keep shipping agents, and the useful work has moved to the layer that coordinates them. That layer is where the next round of switching costs sits. A developer who has tuned prompts, permissions and review habits around one workspace won't move for a marginal model gain.
Meta Conductor acquisition logic follows that pattern. Models change every few months. The workspace is what people learn, and learned habits are stickier than benchmark scores.
A lab that already ships a coding agent has an obvious reason to own the layer that decides which agent gets which task and how the results come back together.
There's a counterargument worth stating. Orchestration tools are thin compared with models, and a lab with enough engineers can rebuild one in a quarter. Meta evidently didn't want to spend that quarter.
What Conductor users should do before the cloud closes
Export anything you need from the cloud before November 20, because deletion starts on that date and doesn't wait for a support ticket. Keep the local install if your workflow depends on it, since core local features survive into early next year.
Then hold off on rebuilding your setup until Holtz's promised news lands. He says it comes by early next year, which is vague enough to plan around but not specific enough to wait on.
If your team runs more than two agents in parallel, start the migration now rather than in the last week. Moving a workspace is tedious. Rebuilding one from memory after a shutdown is worse, and nobody at Meta has promised to help you do it.
What the Meta Conductor deal leaves open
Three things stay unknown: the price, the product's shape under Meta, and whether existing customers get a migration path. The only date on the calendar is November 20.
For Meta, the bet is that AI coding tools get coordinated rather than multiplied. For Conductor's users, the bet is smaller and more immediate: get your work out before the server stops answering, and keep a copy of anything you'd hate to describe again from scratch.






