Meta buys Conductor to expand its AI coding capabilities
Meta has acquired Conductor, an AI coding startup founded in 2024 that enables users to start software projects with multiple agents operating in parallel workspaces. Meta confirmed the transaction to TechCrunch but did not disclose the price or further deal terms.
Conductor founder and chief executive Charlie Holtz announced that the company is joining Meta. He said Conductor has “big, crazy plans for the next interface” and indicated that customers could see something new by early next year.
Parallel agents for compartmentalised software work
Conductor launched its core product only last summer. Its agentic teams are designed to help engineers tackle separate, compartmentalised parts of a software project in concert. The teams can be deployed in the cloud, locally or through a user’s phone.
The platform does not develop the underlying agents itself. Instead, it uses agents from major AI labs, including Anthropic and OpenAI. That architecture positioned Conductor around orchestration and the workflow used to divide and coordinate coding tasks.
Holtz said Conductor’s core features will continue to operate as before until early next year. The important exception is its cloud service, which is scheduled to shut down on November 20; the company will then begin deleting user cloud data.
A further move in Meta’s coding-agent strategy
The deal adds to Meta’s recent effort to close ground in AI services. In August, the company launched Muse Code, its own coding agent. Its trajectory also connects with Meta expands agentic coding with Muse Spark as Meta brings more agentic coding capabilities into its product portfolio.
Meta has also said that its recently launched Muse agents have passed 10 million users. Holtz said he was looking forward to working with Meta chief AI officer Alexandr Wang and Nat Friedman, who leads product at the company’s Superintelligence Labs.
For organisations using Conductor, the immediate operational issue is the November 20 cloud closure and the planned deletion of cloud data. Teams should identify affected projects, preserve the material they need and assess where those workloads will run as Meta sets out its next product plans.