Meta acquires Conductor, and Conductor Cloud shuts down November 20
Updated: 3 minutes ago
Meta has acquired Conductor, the startup behind a desktop and cloud app that runs several AI coding agents in parallel on the same codebase. Conductor announced the deal on November 4, 2026, in a post on its website and in the release notes of version 0.93.0 of its app, and Meta confirmed the acquisition while declining to share financial terms or further details. No price has been disclosed by either company.
The announcement comes with a short wind-down schedule for existing users. New sign-ups and app downloads stopped on November 4, Conductor Cloud becomes read-only on November 13, and the cloud service shuts down on November 20, after which Conductor will begin deleting cloud user data. The local Mac app keeps receiving new models and critical bug fixes until early 2027, when it starts to wind down as well. Current Pro subscribers keep their paid features at no cost, and active subscribers are eligible for a refund.
Conductor's chief executive, Charlie Holtz, wrote in a post on his X account that "Conductor is joining Meta" and said the team has "big, crazy plans for the next interface," with something new for customers promised by early next year. Holtz also named Alexandr Wang, Meta's chief AI officer, and Nat Friedman, who leads product at Meta Superintelligence Labs, as the people he expects to work with. Meta has not said which products the Conductor team will work on, although the company already sells its own coding agent, Muse Code, and an API for its Muse models.
··········
WHAT CONDUCTOR DOES FOR CODING AGENT USERS.
Conductor does not train or sell its own model. The company describes its product as a platform for running teams of coding agents, and its website says it runs "the first-party Claude Code, Codex, Cursor, and OpenCode agents under the hood." Developers bring their own subscriptions and API keys, so the usage of Anthropic, OpenAI or Cursor models is billed by those providers and Conductor sits on top as the orchestration layer.
The core idea is parallel work. Conductor creates isolated copies of a repository, starts an agent in each copy, and lets the developer review and merge what each agent produced. A developer can, for example, give one agent a refactor, a second a bug fix and a third a new test suite, then compare the three results side by side before merging anything. The company added a multiplayer mode in which teammates share a workspace link, see who is active and prompt agents together in real time.
Conductor Cloud extended the same model to remote machines. According to the company, cloud agents ran in isolated microVMs with the repository and its dependencies preinstalled, with sandboxes that start in seconds so agents can keep working for hours. An iPhone app let users check on those agents away from the desk, and a Conductor API allowed teams to build their own integrations. The website lists a SOC 2 Type II report and states that the product is "trusted by 100k+ builders."
The last release before the acquisition shows how closely Conductor tracked the agents it wraps. Version 0.93.0 added GPT-6.1 Terra to the Codex model picker and updated the Claude account usage display to handle newer usage-limit data reported by Claude Code, alongside fixes for chat history, agent-to-agent messages and pull request titles.
··········
CONDUCTOR CLOUD SHUTDOWN TIMELINE AND WHAT USERS NEED TO DO.
The practical consequences fall on two groups: teams that relied on Conductor Cloud for long-running agents, and individual developers who use the local Mac app every day. The schedule published by Conductor is the following.
........
Date | What changes | Who is affected |
November 4, 2026 | New sign-ups and downloads stop; free users can no longer upgrade; Pro features become free for current Pro users | New users, free and Pro users |
November 13, 2026 | Conductor Cloud turns read-only: old chats can be read and exported, no new messages; active subscribers refunded | Cloud users, paying subscribers |
November 20, 2026 | Conductor Cloud shuts down and deletion of cloud user data begins | Cloud users |
Until early 2027 | Local app still gets new models and critical bug fixes | Mac app users |
Early 2027 | Local app begins winding down; all user data deleted when the app shuts down | All remaining users |
........
Cloud users have about two weeks to move their work. Conductor gives two routes. To keep a cloud workspace together with its chats, users right-click the workspace and choose Transfer to local, which moves it onto their Mac. To keep a full copy of their account data, they go to Settings → Account → Export data. Both steps should be completed before November 13 for anyone who still wants to send messages to cloud agents while reviewing what to keep, and in any case before November 20, when deletion starts.
Code that agents already pushed to a remote Git host is unaffected, because Conductor works on copies of repositories the user controls. What disappears with the cloud service is the working state held inside Conductor: unmerged agent branches that were never pushed, chat transcripts, and the file trees of archived cloud workspaces. Teams that used cloud agents for overnight jobs should check every active workspace for unpushed work.
For local users the short-term impact is smaller. The Mac app keeps working with the Claude Code, Codex, Cursor and OpenCode agents already installed on the machine, and Conductor says it will keep adding new models until early 2027. Conductor says it hopes to have a successor ready by then, but neither Conductor nor Meta has described it, named a price or said whether it will support agents from other labs.
On data, Conductor states that it has never sold user data or trained models on it and does not plan to start. The company says all user data will be deleted when the app shuts down in early 2027.
··········
CONDUCTOR'S GROWTH BEFORE THE META DEAL.
Conductor was founded in 2024 by Charlie Holtz and Jackson de Campos and built its first version during the summer of 2025 to get more out of coding agents. In March 2026 it raised a $22 million Series A led by Spark and Matrix, with participation from Y Combinator and the founders of Notion and Linear. In the Series A post, the founders said usage had grown tenfold since January and that engineers at Google, Meta, Amazon, Spotify, Datadog, Ramp, Block and other companies were using the product, in some cases dozens per company.
That customer list is one reason the acquisition reads as a product and talent deal for Meta. Meta engineers were already among the product's users before the acquisition, and Conductor's founders had described an ambition to manage large AI organizations from any device, including a phone or a private cloud. Those are the same workflows the frontier labs are now trying to own directly inside their own agents.
··········
[[ADPLUS_300x250_1]]
META MUSE CODE AND THE SUPERINTELLIGENCE LABS CODING STACK.
Meta entered the coding agent market in August. On August 5, 2026, it released Muse Code as an early beta: a terminal agent built around Muse Spark 1.2, a reasoning model with a 1M-token context window. Muse Code already splits large jobs into tasks for subagents, and each subagent can work in its own Git worktree so parallel changes do not collide, the same isolation principle Conductor applied across agents from different vendors. Every subagent, tool call and decision is written to a per-session JSONL event log, and the `muse resume` command restarts a session from its last recorded step.
Muse Code left beta on August 31 with inter-session messaging, a workflow feature that orchestrates teams of subagents, a rewind command, a TypeScript SDK in developer preview and three subscription plans that Meta described as cheaper than pay-as-you-go pricing. Meta has not published the plan prices in text form. On the Meta Model API, Muse Spark 1.2 was listed at the launch at the following pay-as-you-go rates.
........
Muse Spark 1.2 on Meta Model API | Price per 1M tokens |
Input | $1.25 |
Cached input | $0.15 |
Output (thinking tokens billed as output) | $4.25 |
........
The model line has moved quickly since then. On October 12, Meta introduced Muse Wonder and Muse Wonder Full, which it calls its most capable models to date, making Muse Wonder available through the Meta Model API and Muse Code and reserving Muse Wonder Full for Muse Code subscribers. Three days later it released an open-weight model for coding and agent work, covered in our report on Muse Spark Open with 816B parameters and a 1M-token context. Our earlier analysis of Muse Spark 1.3 and Muse Code describes how Meta positioned the agent for long-horizon work.
Conductor brings Meta something its own stack does not yet show publicly: a graphical interface for supervising many agents at once, a cloud runtime for agents that run for hours, a mobile client and multiplayer workspaces. Muse Code is a terminal tool, and Meta's published Muse Code announcements do not describe a hosted cloud runtime or a mobile app for it.
··········
META AND OPENAI BUY CODING AGENT TOOLS ON THE SAME DAY.
The Conductor deal was announced on the same day OpenAI said it plans to acquire Pierre Computer Company, whose Code Storage service provides Git hosting built for agents, as detailed in our article on OpenAI's plan to bring Pierre's Code Storage into Codex. The two acquisitions target different layers. Pierre supplies the storage and version control that agents write into, while Conductor supplied the interface where developers launch, watch and merge the work of several agents.
Both deals move tooling that sat between developers and the model providers into the labs themselves. Conductor was useful in part because it was neutral: one window could run Claude Code next to Codex and Cursor, with each billed through the user's existing subscription. A Meta-built successor may keep that openness or may center on Muse models, and Meta has said nothing on that point. Developers who chose Conductor for its multi-vendor design should plan on the assumption that the current product ends in early 2027 and treat any successor as a separate decision.
··········
META'S CONDUCTOR ACQUISITION: CONFIRMED FACTS AND OPEN QUESTIONS.
The confirmed facts come from Conductor's own announcement and release notes and from Meta's confirmation of the deal. Meta has acquired Conductor; the price and terms are undisclosed; sign-ups closed on November 4; Conductor Cloud turns read-only on November 13 and shuts down on November 20, with data deletion starting afterwards; the Mac app keeps receiving models and critical fixes until early 2027; current Pro users get paid features free and active subscribers receive refunds.
Several questions remain open. Meta has not said whether the Conductor team will work on Muse Code, on a new product or on internal developer tools, and it has not said whether a successor will run third-party agents such as Claude Code and Codex. Neither company has disclosed how many of the more than 100,000 users relied on the cloud service, and the refund policy is described only as applying to recent, active subscribers. For now, the dates that matter to users are November 13 and November 20, and the steps are concrete: transfer cloud workspaces to a local machine, export account data, and push any unmerged agent work to a Git remote before the cloud goes dark.
··········
FOLLOW US FOR MORE.
·····
DATA STUDIOS
·····
datastudios.org
