Meta Conductor: The agent-orchestration app Conductor is joining Meta. That is confirmed by CEO Charlie Holtz’s official announcement and by TechCrunch on November 4, 2026. Neither side disclosed the purchase price or contract terms.
Conductor lets developers run multiple coding agents in parallel, isolated workspaces — including Claude Code and Codex via users’ own subscriptions and keys. The cloud tier and the local Mac app are winding down on a staged schedule; Meta confirmed the acquisition to TechCrunch without further comment.
Meta Conductor: user timeline
Per Conductor’s announcement, as of November 4 there are no new sign-ups or app downloads. Existing free users can no longer upgrade to Pro; Pro users keep Pro features for free. On November 13, Conductor Cloud becomes read-only (chats readable/exportable, no new messages); active subscribers get a refund. On November 20 the cloud shuts down and deletion of cloud user data begins.
Local Conductor is expected to keep working and to receive new models plus critical bug fixes until early 2027. After that the team hopes to ship a “new interface” under Meta — without a public spec. Cloud workspaces can be moved with right-click “Transfer to local”; a full archive export lives under Settings → Account → Export data.
Product and context
Conductor (formally Melty Inc.) launched in July 2025 by its own timeline and positioned itself as an orchestration layer over third-party agents, not as a frontier model of its own. SiliconANGLE and Axios report use inside large engineering orgs and Meta engineers before the deal; Axios notes OpenAI’s planned Pierre Computer acquisition the same day — industry context only, without mixing OpenAI deal details into this story.
Meta has been expanding its own coding offers such as Muse Code. Whether Conductor’s tech lands in Muse, Superintelligence Labs, or a new product is not stated publicly. Holtz pointed on X to working with Alexandr Wang and Nat Friedman; that is intent, not a roadmap.
What teams should do now
Cloud users: export or transfer before November 20. Local users: plan for models and critical fixes only into early 2027 and document dependencies. Privacy: Conductor says it has never sold or trained on user data and will delete Conductor user data when the app shuts down in early 2027 — that does not replace your own compliance review.
On code404zero we regularly cover agent tooling: Rebuilding Manus, Paperclip, BetterClaw, and GitHub Copilot Fusion. Conductor fits the wave of selling orchestration rather than a single model — and shows how quickly such products can fold into lab acquisitions.
What Conductor was technically
Conductor orchestrated third-party agents across parallel, isolated codebase copies and offered review/merge paths for their output. Supported agents reportedly included Claude Code, Codex, and Cursor — billed through user keys. Desktop on Mac; cloud in sandboxed VMs that could run for hours, plus an iPhone companion app. A March Series A from Spark Capital and Matrix, with Y Combinator and Notion/Linear founders among backers (secondary reporting).
The value sat less in a proprietary frontier model than in UX and parallelization. That layer matters to labs scaling coding agents without building every orchestration surface themselves. Whether Meta keeps Conductor’s cloud architecture or mainly talent and product ideas is not publicly evidenced.
Export deadlines and operational risk
The hard data dates: cloud read-only on November 13, deletion starting November 20. Teams with CI hooks, chat history, or workspace config in the cloud risk knowledge loss if local transfer fails. Conductor offers transfer-to-local and account export; compliance-minded teams should version exports and document access.
Local continuity into early 2027 is not a blank check: “new models and critical bug fixes” is not a feature roadmap or a guarantee about third-party agent APIs. Anyone who wired Conductor deep into daily work needs a Plan B in parallel (other orchestration, IDE-native agents, internal wrappers).
A grounded reading
The acquisition is real and dated; the price is not. For end users the shutdown calendar matters more than speculation about Meta’s coding roadmap. For competitors, the deal signals that agent orchestration is strategically valuable enough for big-tech M&A — without proving what “early next year” will look like.
Meta context without speculation
In the months before the deal Meta emphasized coding agents and Muse products; Conductor adds orchestration and a fast shipping cadence — that is the Axios/TechCrunch framing, not a Meta press release with a roadmap. Holtz teases “something new … early next year” without a feature list. Until then, the shutdown dates are the only hard commitments to users.
For competitors (other agent IDEs and orchestrators), the deal is a demand signal: parallel-agent UX is acquisition-worthy. Whether that shifts pricing, talent markets, or open-source alternatives is something to watch — not a forecast.
In short: Meta Conductor means no new sign-ups from November 4, cloud shutdown on November 20, and local continuity into early 2027. Primary sources are Conductor’s announcement and Meta’s confirmation to TechCrunch.
