Meta Acquires Conductor, the AI Coding Agent Startup
Conductor's team is joining Meta after its app for running rival AI coding agents side by side caught on with developers. Here's what changes, and when.
Meta has acquired Conductor, a two-year-old startup whose desktop app lets developers run several AI coding agents — including Claude Code, Codex, Cursor and OpenCode — in parallel, each working on its own isolated copy of a codebase, so a developer can compare the results and merge whichever one did the best job. Conductor announced on November 4, 2026, that its whole team is joining Meta; financial terms were not disclosed. Conductor Cloud, the startup’s hosted version, goes read-only on November 13 and shuts down on November 20, while the local Mac app keeps receiving new models and critical fixes until early 2027.
The short version
- What: Meta acquires Conductor, maker of a Mac app that runs multiple AI coding agents side by side on isolated branches of the same repo.
- When: Announced November 4, 2026. Terms not disclosed.
- Conductor Cloud: Read-only November 13, shuts down November 20. Existing data is later deleted.
- Local app: Keeps working, with model updates and bug fixes, until early 2027.
- Founders: Charlie Holtz (CEO) and Jackson de Campos (CTO), who started the company in 2024 through Y Combinator.
What happened
Conductor published the news itself, in a company announcement signed by Holtz and nine teammates: “I have big news: Conductor is joining Meta.” The post does not name a purchase price, and as of publication Meta has not put out its own newsroom statement confirming the deal or its terms — the acquisition is confirmed only by Conductor’s own post and by press reports citing people familiar with the matter. Readers should treat any detail that appears only in press coverage, rather than in Conductor’s own announcement, as reported but not independently confirmed.
What is confirmed, directly from Conductor: the deal was announced November 4, 2026; new sign-ups and app downloads stopped that same day; and the product is being wound down on a fixed schedule rather than being folded into Meta immediately.
What Conductor actually does
Conductor is a native Mac application, not a coding agent of its own. According to the company’s documentation, it sits on top of existing AI coding tools — Claude Code, OpenAI’s Codex, Cursor and OpenCode are the four it names as supported “harnesses” — and gives each one its own Git worktree: a separate working copy of a repository, on its own branch, that the agent can edit without touching the developer’s main checkout or any other agent’s workspace.
That isolation is the point. Instead of running one agent at a time and hoping it picks the right approach, a developer can launch the same prompt against two or three agents at once, then open Conductor’s built-in diff viewer to compare their results side by side and merge the one that worked. The app also adds the connective tissue that makes this practical day to day: GitHub and Linear integration, checkpoints, PR creation, code review tooling, and — in the hosted version — cloud workspaces so agents can keep running when a laptop is closed.
Developers already used to running one assistant inside an editor, such as Cursor’s AI-assisted code editor, will recognize the underlying idea; Conductor’s pitch is to make running several such agents at once, instead of one, manageable.
The deal, and what is still just reported
Conductor’s own post confirms the team is joining Meta but does not say which part of Meta. Multiple outlets have reported that the team is headed to Meta Superintelligence Labs (MSL), the division Meta formed in mid-2025 to centralize its AI research and product work, and that Holtz described the move in terms of working alongside MSL leadership. None of that has been confirmed in an official Meta statement that this article could independently verify, so it should be read as reported, not confirmed.
What is unambiguous is the timing: Meta shipped its first MSL-branded coding agent, Muse Code, running on the Muse Spark 1.2 model, in August 2026, positioning it as a lower-cost rival to Claude Code and Codex. Acquiring a team that has spent two years building the orchestration layer on top of exactly those competing agents is a logical way for Meta to accelerate its own coding-agent roadmap, whether or not Conductor ends up supporting outside agents going forward.
Conductor Cloud’s shutdown timeline
Conductor laid out a specific, dated wind-down for its hosted product in its announcement. The table below reflects exactly what the company published.
| Date | What happens |
|---|---|
| November 4, 2026 | New sign-ups and app downloads stop. Existing free users can no longer upgrade to Pro; existing Pro subscribers keep Pro features at no charge. |
| November 13, 2026 | Cloud workspaces become read-only. Users can still read old chats and export data but cannot send new messages. Active Cloud subscribers are refunded. |
| November 20, 2026 | Conductor Cloud shuts down. Deletion of Cloud user data begins; the company tells users to export their data before this date. |
| Early 2027 | The local desktop app, which keeps working normally until then, is expected to begin winding down as a new interface is introduced. |
For anyone still using Conductor Cloud, the company points to two options before the November 20 cutoff: right-click a cloud workspace and choose “Transfer to local” to move it (and its chat history) onto the Mac app, or go to Settings → Account → Export data to download an archive.
What happens to the local app
The Mac app — the original, non-cloud product — is not shutting down on the same schedule. Conductor says it will keep receiving new model support and critical bug fixes “until early 2027,” at which point the company plans to wind it down in favor of a new interface it has not yet detailed. Conductor has not said whether that future interface will keep supporting today’s third-party agents — Claude Code, Codex, Cursor and OpenCode — and some reporting has flagged that continuity as an open question rather than a settled one. Readers planning around Conductor long-term should treat that specific point as unresolved rather than assume either outcome.
Developers who rely on running several agents against git worktrees in the meantime have a non-Conductor fallback worth knowing about: the same pattern is documented for Claude Code and Codex directly, and tools built around other CLIs are evolving quickly, as this site covered in its look at how one coding CLI’s interface changed and what migrating looks like.
Conductor’s data-handling claim
In the same announcement, Conductor states that it “has never sold or trained on” user data and says it does not intend to start. That is a claim made by the company about its own past and intended future practice, not a third-party audit finding, and it is worth noting precisely because the company is now under new ownership: Meta inherits whatever data Conductor holds, and the stated policy is what Conductor has published, not a term independently verified by Pandromeda. Cloud user data is scheduled for deletion once the hosted service shuts down on November 20, which is also why the company is urging an export beforehand.
Company background: founders and funding
Conductor was started in 2024 by Charlie Holtz and Jackson de Campos, who went through Y Combinator’s Summer 2024 batch. The two met playing ultimate frisbee at Brown University; before Conductor, Holtz had worked as a quant researcher at hedge fund Point72 and led growth at Replicate, while de Campos had built machine-learning infrastructure at Netflix and researched automated negotiating agents at Brown. The pair had previously built a command-line party-hosting tool called Shindig together before turning to Conductor.
In March 2026, Conductor announced a $22 million Series A, with Matrix Partners (whose Ilya Sukhar had led its seed round and joined the board) and Spark Capital (represented by Nabeel Hyatt) both participating, alongside Y Combinator and the founders of Notion and Linear. In that same post, the founders said Conductor’s user base had grown tenfold since the start of 2026 and that they intended to expand the product from a tool for small teams of agents on a single Mac into a platform for managing much larger AI-driven engineering organizations.
| Fact | Detail |
|---|---|
| Founded | 2024 (Y Combinator, Summer 2024 batch) |
| Founders | Charlie Holtz (CEO), Jackson de Campos (CTO) |
| Headquarters | San Francisco, California |
| Known funding | $22M Series A, announced March 30, 2026 — led by Matrix Partners and Spark Capital, with Y Combinator participating |
| Core product | Mac app for running Claude Code, Codex, Cursor and OpenCode in parallel on isolated git worktrees |
| Acquired by | Meta, announced November 4, 2026; terms undisclosed |
Why this deal fits a broader pattern
Conductor is not the only coding-tooling acquisition announced that week. On the same day Conductor confirmed its deal with Meta, OpenAI announced it would acquire Pierre Computer Company, maker of the Trees and Diffs open-source libraries and a distributed Git backend called Code Storage, specifically to strengthen Codex. The two deals are unrelated — different buyers, different targets, different products — but together they point to the same underlying trend: as coding agents from Anthropic, OpenAI, Google, Meta and others multiply, the tooling that sits around those agents — version control, code review, orchestration, isolation — has become something the model labs themselves want to own rather than leave to independent startups.
For Meta specifically, the logic is straightforward even without an official statement explaining it: the company launched its first in-house coding agent, Muse Code, only three months before the Conductor deal, and buying a team that has spent two years building the interface layer for running multiple competing agents side by side is a fast way to get orchestration expertise in-house.
How Conductor fits among AI coding tools
It helps to be precise about what Conductor is not. It is not a model, and it is not a replacement for the agents developers already use — it is a management layer that sits above them. That distinguishes it from a standalone editor or agent such as Cursor, and from command-line tools that run a single agent against a single checkout. Conductor's bet, stated plainly in its own Series A announcement, was that "most software will soon be built by AI teams" rather than individual AI assistants, and that those teams would need a dedicated interface for comparing, steering and merging several agents' work rather than babysitting one at a time. Whether that bet pays off inside Meta, under a different roadmap and possibly a narrower set of supported agents, is now an open question rather than a product decision Conductor's own founders still control.
What happens next
For current Conductor users, the near-term to-do list is concrete: anyone on Conductor Cloud should export data or transfer workspaces to the local app before November 20, since cloud data deletion begins after that date. Pro subscribers keep their paid features for free going forward but cannot expect new Cloud functionality. Everyone running the local Mac app can keep using it as-is, with continued model updates and bug fixes promised through early 2027.
What is worth watching after that: whether the “new interface” Conductor has promised for early 2027 keeps its multi-agent, multi-vendor approach — letting developers keep running Claude Code, Codex, Cursor and OpenCode side by side — or whether it narrows toward Meta’s own Muse Code and other in-house tools once the team is fully absorbed into Meta Superintelligence Labs. Also worth watching is whether Meta ever issues its own public statement on the acquisition's terms, team size, or product plans; none of that has been confirmed on Meta's own channels as of this writing, only reported by outlets citing people familiar with the deal.
Frequently asked questions
Did Meta confirm what it paid for Conductor?
No. Conductor's own announcement says the team is joining Meta but does not name a price, and as of publication Meta has not issued its own public statement confirming the deal or its terms.
When does Conductor Cloud shut down?
Conductor Cloud becomes read-only on November 13, 2026, and shuts down on November 20, 2026, after which the company begins deleting Cloud user data.
What should I do with my Conductor Cloud data before the shutdown?
Conductor says users can right-click a cloud workspace and choose "Transfer to local" to move it to the Mac app, or go to Settings, then Account, then Export data to download an archive, before November 20.
Will the local Conductor desktop app stop working?
Not immediately. Conductor says the local Mac app keeps working normally and keeps receiving new model support and critical bug fixes until early 2027, when the company plans to wind it down in favor of a new interface.
Which AI coding agents does Conductor support?
Conductor's documentation lists Claude Code, OpenAI's Codex, Cursor and OpenCode as supported agents, each run in its own isolated git worktree so results can be compared and merged.
Is this related to OpenAI's acquisition of Pierre Computer?
No. The two deals were announced the same week in November 2026 but are unrelated: Meta acquired Conductor, while OpenAI separately announced it would acquire Pierre Computer Company to strengthen its own Codex tool.
Sources
- Conductor: "Conductor is joining Meta" (official announcement)conductor.build
- Conductor: Changelog 0.93.0 — Conductor is joining Metaconductor.build
- Conductor: Conductor's Series Aconductor.build
- Y Combinator: Conductor company profileycombinator.com
- OpenAI: OpenAI to acquire Pierreopenai.com
- Wikipedia: Meta Superintelligence Labsen.wikipedia.org
Felix Moreau writes Pandromeda's software coverage and how-to guides. He covers Windows, macOS and Linux updates, the apps people rely on, emulators and developer tools, and turns official documentation into clear, numbered steps that work on the current version.


