Meta has acquired Conductor, the startup behind a popular Mac app that lets developers run several AI coding agents side by side. The deal, first reported by Axios on November 4 and confirmed by Meta to TechCrunch, brings Conductor’s team into Meta Superintelligence Labs. For current users, the clock is already running: Conductor Cloud shuts down on November 20.
Key takeaways
- Meta acquires Conductor; financial terms were not disclosed.
- CEO Charlie Holtz, CTO Jackson de Campos and the team join Meta Superintelligence Labs.
- New sign-ups and downloads stopped on November 4. Conductor Cloud goes read-only on November 13 and shuts down on November 20, when deletion of cloud user data begins.
- The local Mac app keeps getting new models and critical fixes until early 2027, then winds down.
- If you use Conductor Cloud, transfer your workspaces to local and export your data now.
What happened
Conductor announced the deal in a short post titled “Conductor is joining Meta,” signed by ten members of its team. Holtz said the group has “big, crazy plans for the next interface” and promised customers “something new” early next year. Neither company has said what that product will be, and Meta declined to share further details with TechCrunch.
According to TechCrunch, Holtz said on X that he is looking forward to working with Alexandr Wang, Meta’s chief AI officer, and Nat Friedman, who leads product at Meta Superintelligence Labs (MSL). In coverage of the announcement, Holtz is also quoted praising MSL’s “talent density.” Several outlets describe the deal as primarily a team acquisition rather than a purchase of the product itself, which fits with the decision to wind Conductor down.
What Conductor actually did
Conductor never built its own AI model. Instead, it acted as an orchestration layer. A developer could spin up several isolated copies of a codebase, assign a separate coding agent to each one, and then review and merge whatever the agents produced. It worked with agents from other companies, including Anthropic’s Claude Code and OpenAI’s Codex, with users bringing their own subscriptions or API keys.
The company was founded in 2024, came through Y Combinator, and launched its product in July 2025. It raised a reported $22 million Series A in March 2026 led by Spark Capital and Matrix. A later cloud product, Conductor Cloud, let those agents run remotely in isolated environments for long stretches, so developers didn’t need to keep their laptops busy. If you are new to the idea of several agents working on one project at once, our explainer on multi-agent coding covers how the approach works.
The shutdown timeline, step by step
Conductor’s announcement and its 0.93.0 changelog lay out the wind-down in clear stages:
- November 4: New sign-ups and downloads stop. Free users can no longer upgrade, and existing Pro users keep Pro features at no charge.
- November 13: Conductor Cloud becomes read-only. You can still read old chats and export data, but you can’t send new messages. Active subscribers receive a refund (the company hasn’t detailed the amount or process).
- November 20: Conductor Cloud shuts down and deletion of cloud user data begins.
- Early 2027: The local Mac app stops getting new models and critical bug fixes, and winds down. Conductor says all user data will be deleted when the app shuts down.
Conductor also says it has never sold or trained on user data and won’t start now.
What Conductor users should do now
If you rely on Conductor, here’s a practical checklist based on the company’s own instructions:
- Move cloud work to your Mac. Right-click each cloud workspace and choose Transfer to local. This brings the workspace and its chats onto your machine.
- Export everything. Go to Settings → Account → Export data and download a full copy. Do this before November 13 if you want to keep working in the cloud until then, and absolutely before November 20.
- Push your branches. Agent work that only exists in a cloud workspace is the easiest thing to lose. Make sure any useful branches are committed and pushed to your own Git host.
- Check your agent keys. Because Conductor ran agents on your subscriptions or API keys, nothing changes with those accounts. But if you created keys just for Conductor, consider rotating or revoking them once you’ve migrated.
- Plan your replacement. The local app works until early 2027, which buys time, but it is a sunset product. Start testing alternatives now rather than in January.
Why it matters
The deal says a lot about where the AI coding race is heading. For the past year, competition has centred on models: which one writes the best code, solves the most benchmark tasks, or runs the longest. Conductor’s value was in the layer above the model. It treated agents from rival labs as interchangeable workers and gave developers one place to manage them.
That layer is becoming strategic. Meta already has its own coding agent, Muse Code, which launched in August 2026, according to TechCrunch. Buying a team that has spent two years building interfaces for directing many agents at once suggests Meta wants more than a single assistant in an editor. Holtz’s phrase “the next interface” points in the same direction: the bet is that developers will increasingly supervise groups of agents rather than chat with one.
It is also a reminder of a familiar risk. Many popular AI developer tools are small startups sitting on top of models owned by much bigger companies. When one of those startups is acquired, the product can disappear quickly. Conductor users got roughly two weeks’ notice before the cloud service stops.
What it means for developers and teams
For individual developers, the immediate job is migration. The bigger lesson is to keep your workflow portable. Conductor was easier to leave than many tools because it ran on your own agent subscriptions and offered tools to pull cloud work back to your machine. Tools that hold your history, prompts or code only in their own cloud are harder to exit.
For engineering leads, this is a good moment to write down which agent tools your team depends on, where their data lives, and how you’d move off each one. If your team is comparing the main options, our Claude Code vs Cursor comparison is a useful starting point.
For founders building agent tooling, the takeaway cuts both ways. Big labs clearly see value in orchestration teams, which is good news for acquisition prospects. But it also means the companies whose models you depend on may soon compete directly with you on the interface.
What to watch next
- The “something new” promised for early 2027. Watch whether it ships as part of Muse Code, as a standalone Meta developer product, or inside Meta’s internal tools first.
- Multi-vendor support. Conductor worked with Claude Code and Codex. It’s an open question whether a Meta product would support rival agents or focus on Meta’s own models.
- Refund details. Conductor says active subscribers will be refunded, but hasn’t explained the amount or process yet.
- More deals like this. As coding agents become commodities, expect more acquisitions of the tools that sit between developers and models.
For now, if you have anything in Conductor Cloud, the most important date is November 20. Export first, then think about what comes next.