Meta Conductor Acquisition: What the November 20 Cloud Shutdown Means for Developers
On 4 November 2026, Meta bought Conductor, the Mac app that lets developers run several AI coding agents at once — and gave its cloud users just sixteen days to get their work out. The Meta Conductor acquisition is a small deal by Meta’s standards, with no price disclosed, but it carries a hard deadline that thousands of developers cannot ignore: Conductor Cloud becomes read-only on 13 November 2026 and shuts down completely on 20 November 2026, when the company begins deleting cloud user data.
If you run coding agents through Conductor Cloud, this guide explains what the Meta Conductor acquisition changes, the exact shutdown dates, how to move your workspaces to your Mac or export your data before the deadline, what happens to the local app, and which alternatives are worth testing now — before your workflow disappears with the service.

Table of Contents
- Meta Conductor Acquisition at a Glance
- What Is Conductor?
- What Happened in the Meta Conductor Acquisition
- The Shutdown Timeline: Every Date That Matters
- How to Export Your Conductor Data Before November 20
- What Happens to the Local Mac App?
- What Meta Gets — and What It Might Build Next
- Best Conductor Alternatives in 2026
- What the Meta Conductor Acquisition Says About AI Coding
- Meta Conductor Acquisition FAQ
- Bottom Line: Your Checklist Before November 20
Meta Conductor Acquisition at a Glance
If you only have sixty seconds, here is everything the Meta Conductor acquisition means in practice. Meta acquired Conductor on 4 November 2026, Axios first reported the Meta Conductor acquisition, and Meta confirmed it to TechCrunch without disclosing financial terms. Conductor stopped accepting new sign-ups and app downloads the same day.
Conductor Cloud becomes read-only on 13 November 2026, shuts down on 20 November 2026, and deletion of cloud user data begins on that date. The local Mac app keeps receiving new model support and critical bug fixes until early 2027, then it too begins winding down. Under the Meta Conductor acquisition, Conductor’s team, led by founder and chief executive Charlie Holtz, is joining Meta Superintelligence Labs to work on a new interface expected in early 2027.
Active subscribers will receive refunds, and existing Pro users keep their paid features at no charge until the shutdown. The one action that matters this week is simple: move your cloud workspaces to your Mac or export your data before 20 November — ideally before 13 November, while the cloud is still fully working.
| Detail | What we know |
|---|---|
| Announcement date | 4 November 2026 |
| Buyer | Meta (team joins Meta Superintelligence Labs) |
| Price | Not disclosed |
| New sign-ups and downloads | Stopped 4 November 2026 |
| Conductor Cloud read-only | 13 November 2026 |
| Conductor Cloud shutdown | 20 November 2026 — cloud data deletion begins |
| Local Mac app | Supported with new models and bug fixes until early 2027 |
| Refunds | Active subscribers to be refunded; amount and schedule not published |
| Next product | A new interface is promised for early 2027; no details yet |
What Is Conductor?
To understand why the Meta Conductor acquisition matters, you first need to understand what Conductor actually does — because it builds no AI models of its own. Conductor is a Mac application that gives developers one control panel for running several AI coding agents at the same time, each in its own isolated workspace. Instead of juggling five terminal windows, you assign different pieces of a project to different agents, watch them work side by side, review their changes, and merge the good ones. One agent can refactor the authentication module while another writes tests for the payment flow and a third updates the documentation, all without stepping on each other’s files.
Conductor was founded in 2024 by Charlie Holtz and chief technology officer Jackson de Campos, a San Francisco startup that went through Y Combinator’s Summer 2024 batch. The company raised a $22 million Series A funding round in March 2026 from Spark Capital and Matrix, and by the time of the Meta Conductor acquisition it reported more than 100,000 users. That is a modest user base next to the millions using GitHub Copilot or ChatGPT, but Conductor’s users were unusually committed: developers who had rebuilt their daily workflow around parallel agents, with cloud workspaces holding the history of long-running projects.

How Conductor Works in Practice
The core idea behind Conductor is simple, and it explains why the Meta Conductor acquisition caught the attention of the whole AI coding world. Modern coding agents such as Claude Code and OpenAI Codex are powerful, but each one traditionally works alone, in one terminal, on one task. Conductor wraps them in a workspace model. Every agent gets its own isolated environment — its own copy of the code, its own conversation, its own sandbox — so agents can work in parallel without overwriting each other’s changes. The developer becomes a supervisor rather than a typist: assigning tasks, checking diffs, approving merges, and stepping in only when an agent goes off track.
Conductor supports the agents developers already use, including Claude Code, OpenAI Codex, Cursor and OpenCode, running them side by side rather than forcing a choice between them. That agent-neutral design was part of its appeal. A team could run Claude Code on the hardest refactoring, Codex on a quick bug fix, and Cursor on a UI change, all from the same window. Conductor Cloud extended the same idea beyond one machine, hosting workspaces in the cloud so developers could start agent work from anywhere and check on it later. It is that cloud service — not the local app — that the Meta Conductor acquisition is shutting down first.
Why Developers Adopted It So Quickly
Conductor arrived at exactly the moment developers stopped supervising one AI coding agent and started supervising a team of them. The complaint it answered was practical, not theoretical: when several agents work on the same repository, somebody has to keep their changes separate, track which agent did what, and make sure two agents do not edit the same file at the same time. Conductor turned that coordination work into a visual interface — workspaces in a sidebar, live status for each agent, and a review step before anything lands in the main codebase.
The timing also mattered. Throughout 2026, the biggest coding-agent launches all pointed in the same direction: agents that run longer, handle bigger tasks, and work with less supervision. Anthropic shipped message threads so long-running agents would stop resending entire conversations, and OpenAI kept pushing Codex deeper into multi-step work. Conductor sat on top of all of them as the orchestration layer — the desk where the work gets organised, rather than the worker doing it. That is precisely the layer Meta bought in the Meta Conductor acquisition, and it is why the Meta Conductor acquisition is about much more than one small startup’s fate.
What Happened in the Meta Conductor Acquisition
The Meta Conductor acquisition became public on Tuesday, 4 November 2026. Axios first reported the Meta Conductor acquisition, citing sources, and founder and chief executive Charlie Holtz confirmed it on Conductor’s blog the same day with the words: “I have big news: Conductor is joining Meta.” Meta confirmed the Meta Conductor acquisition to TechCrunch but declined to share further details, and neither company has disclosed a purchase price, a stock-versus-cash split, or the exact number of people joining Meta.
Holtz said the team is joining Meta Superintelligence Labs, the company’s AI organisation, where he looks forward to working with chief AI officer Alexandr Wang and product head Nat Friedman. The Meta Conductor acquisition announcement also promised something new: the team is working toward a new interface, with something expected in early 2027. What that interface is, whether it will be a coding tool at all, and whether existing Conductor users will get any kind of migration path to it — none of that has been announced. For now, the only certainty is the wind-down schedule, and it is moving fast.
How the Meta Conductor Acquisition Was Announced
The way the Meta Conductor acquisition was announced tells its own story. There was no joint press release with a price, no product roadmap, and no migration plan — just a short blog post from the founder, a confirmation to one publication, and a detailed shutdown notice for users. The Meta Conductor acquisition follows a familiar pattern in acqui-hires, where the buyer wants the team more than the product: the product winds down on a short timetable while the people move to the buyer’s organisation. Meta already has its own AI coding product, Muse Code, but neither company has confirmed that Conductor users will be migrated to it, or that Conductor’s features will be folded into it.
It is also worth noting what happened on the same day. On 4 November 2026, OpenAI said it would fold Pierre’s Code Storage into Codex, while Factory absorbed HumanLayer — three coding-tool deals in a single day, with financial terms undisclosed in all of them. The coincidence is the story: the race in AI coding is no longer only about which model writes the best code. The control panel that manages the agents — the orchestration layer — has become an acquisition target in its own right.
Our full coverage of the same-day OpenAI deal is here: OpenAI’s Pierre acquisition and what it means for Codex users.
Who Is Joining Meta
The Meta Conductor acquisition brings Conductor’s team into Meta Superintelligence Labs, the division Meta built in 2026 to consolidate its frontier AI work. Holtz, who founded Conductor in 2024 and served as its chief executive, will work on the promised new interface alongside Wang and Friedman. Chief technology officer Jackson de Campos, his co-founder, is joining Meta as well. No source has disclosed an exact headcount, and Meta has not said how large the Conductor team is, but the company’s $22 million Series A in March 2026 and its 100,000-plus user base suggest a small, senior team — exactly the profile Meta has been hiring aggressively for Superintelligence Labs all year.
For users, the honest reading is this: in the Meta Conductor acquisition, Meta bought the people who built one of the best multi-agent coding interfaces, not the product those people built. That is good news for Meta’s future coding tools and uncertain news for everyone still running projects on Conductor today. The interface Holtz hints at for early 2027 may be excellent — but it does not yet exist, it has no announced price, and there is no promise that anything you built in Conductor will carry over to it. Your job this week is to protect your own work, not to wait for Meta’s next announcement.
The Shutdown Timeline: Every Date That Matters
The Meta Conductor acquisition comes with a precise, staged wind-down, and the dates are the most important facts in this article. Conductor published the schedule in its own announcement and in the version 0.93.0 release notes, and multiple outlets have confirmed the same dates. There are four milestones, and two of them fall within the next ten days.
| Date | What happens | What you can still do |
|---|---|---|
| 4 November 2026 | Conductor joins Meta. New sign-ups and app downloads stop. | Existing users keep working. Free users can no longer upgrade to Pro; current Pro users keep paid features at no charge. |
| 13 November 2026 | Conductor Cloud becomes read-only. | Read old chats and export data. You cannot send new messages to agents. Active subscribers receive refunds. |
| 20 November 2026 | Conductor Cloud shuts down. | Nothing in the cloud. Deletion of Conductor Cloud user data begins. |
| Early 2027 | Local Mac app begins winding down. | Until then, the local app receives new model support and critical bug fixes. No exact shutdown date has been announced. |
November 4: Sign-Ups Stop Immediately
The first stage of the Meta Conductor acquisition wind-down took effect on the day of the announcement. Conductor stopped accepting new sign-ups and stopped offering app downloads on 4 November 2026. If you did not already have an account, you cannot get one now, and if you did not already have the app installed, you cannot download it.
Existing free users can no longer upgrade to Pro — but there is a small consolation: current Pro users keep their paid features at no charge for the remainder of the service’s life. If you are a Pro subscriber, you do not need to cancel anything to stop being charged; active subscribers will receive refunds, although Conductor has not published a specific refund amount or processing schedule.
November 13: Conductor Cloud Goes Read-Only
Friday, 13 November 2026 is the date that changes how you can use Conductor Cloud. From that day, cloud workspaces become read-only: you can still read old chats and export your data, but you cannot send new messages to your agents. Any agent work that is still running in the cloud will stop accepting new instructions, so a half-finished multi-agent task will stall unless you have already moved it. The read-only week is a grace period, not a reprieve — it exists so you can get your data out, not so you can keep working.
That distinction is why every guide to the Meta Conductor acquisition shutdown, including TechRepublic’s, recommends finishing your export before 13 November rather than during the read-only week. Exports remain available after the 13th, but if something goes wrong — a transfer that fails, an archive that will not download, a workspace that will not open — you will have less time and fewer options to fix it. Do the work while the service is still fully operational.
November 20: Shutdown and Data Deletion Begin
Friday, 20 November 2026 is the hard deadline. Conductor Cloud shuts down on that date, and the company says it will begin deleting Conductor Cloud user data. After 20 November there is no cloud service to log into, no workspace to open, and no archive to download. Anything you have not moved to your Mac or exported by then is gone — not archived, not recoverable through support, but deleted. That is the single most important sentence in this article, and it is the reason the Meta Conductor acquisition deserves your attention this week rather than next month.
Early 2027: The Local App Winds Down Too
The local Mac app gets a longer runway, but it is a runway, not a reprieve. Conductor says the locally run application will continue operating and will receive new model support and critical bug fixes until early 2027, after which it begins winding down. The company has not announced an exact shutdown date for the local app, and it has not explained which features, if any, might stop working as support winds down. It has said that it will delete all Conductor user data when the app shuts down. Moving your cloud workspaces to your Mac buys you weeks or a few months — useful breathing room, but not a permanent home. Plan your migration to a long-term alternative during that window, not after it closes.

How to Export Your Conductor Data Before November 20
The Meta Conductor acquisition gives you two official ways to preserve your cloud data, both described in Conductor’s own announcement and its version 0.93.0 release notes. Do both: transfer the workspaces you still need to your Mac, and download a full archive of your account data as a backup. Neither step takes long, and both are free. Work through this section in order, and do not leave it until the read-only week.
Step 1: Transfer Cloud Workspaces to Your Mac
Transferring a workspace moves it — along with its chats — from Conductor Cloud to your local Mac, where it keeps working in the local app until early 2027. This is the option to use for any project you are still actively working on, because it preserves the workspace in a usable form rather than as a static archive.
- Open Conductor on your Mac and find the cloud workspace in the sidebar.
- Right-click the workspace.
- Select Transfer to local.
- Allow the transfer to finish completely, then check that the workspace and its chats are accessible on your Mac before moving on to the next one.
Do this for every cloud workspace you care about, one at a time, and verify each transfer before starting the next. One caution from the coverage of the Meta Conductor acquisition: Conductor has said you can still export data after 13 November, but it has not said that Transfer to local will still work once the cloud is read-only. Do not assume it will. Transfer your workspaces while the cloud is still fully working — this week, not next.
Step 2: Export Your Full Account Data
The second option downloads an archive of all your Conductor account data. This is the safety net: even if a workspace transfer fails, or you later realise you needed a conversation you did not transfer, the archive should contain it. It is also the right step for local-only users, who should export before the app winds down in early 2027.
- Open Settings in Conductor.
- Select Account.
- Choose Export data.
- Download the resulting archive and store it somewhere safe — not only on the same Mac that runs Conductor, but in a backed-up location such as an external drive or encrypted cloud storage.
One honest caveat, flagged by TechRepublic’s guide to the Meta Conductor acquisition shutdown: Conductor has not specified every file or setting the export archive contains, so do not assume the downloaded data will reproduce an entire working environment. Treat the archive as a record of your work — conversations, history, configuration — rather than as a one-click restore. Open the archive after downloading it and confirm that the workspaces and chats you care about are actually inside.
Step 3: Commit and Push Your Code
Conductor workspaces are built on Git repositories, and your code is the one part of your work that does not depend on Conductor at all — provided it is committed and pushed. Before 20 November, go through every repository you have touched through Conductor and make sure every important change is committed and pushed to your remote Git host, whether that is GitHub, GitLab, Bitbucket, or a self-hosted server. Check for uncommitted changes, stashes, and branches that exist only inside a Conductor workspace. An agent’s finished work that was never committed is exactly the kind of thing that disappears with a cloud shutdown.
While you are at it, document anything cloud-specific. If a workspace depends on particular environment settings, dependencies, or credentials to run, write them down now. Secrets should be transferred securely — through your team’s secret manager or an encrypted channel — never copied into an unprotected archive or pasted into a chat. The export archive is a copy of your data, not a secure vault, so handle it accordingly.
Step 4: Check Your Subscription and Refund
If you pay for Conductor, check your subscription status in Settings. Current Pro users keep their paid features at no charge until the shutdown, and Conductor says active subscribers will receive refunds — but it has not published a specific refund amount or processing schedule. Keep an eye on the payment method you used for the subscription and on the email address tied to your Conductor account. If no refund arrives within a few weeks of the shutdown, that email address is the one Conductor will use to contact you, and it is the address you should use if you need to follow up. Do not cancel your subscription in a way that closes your account before you have exported your data.
What Happens to the Local Mac App?
The local Mac app is the better half of the Meta Conductor acquisition story for existing users, but only in the short term. Conductor says the local application will continue operating and will receive new model support and critical bug fixes until early 2027. That means if you transfer your cloud workspaces to your Mac this week, you can keep working in Conductor locally for the next few months, with new AI models added as they arrive and critical bugs fixed if they appear.
What it does not mean is that the local app is safe. The company has not announced an exact shutdown date, has not said which features might stop working first, and has said plainly that it will delete all Conductor user data when the app shuts down. The local app is a bridge, not a destination. Use the months it gives you to evaluate alternatives properly — testing them against your real repositories and your real workflows — rather than treating the local app as a permanent replacement for the cloud service.
There is also a practical question nobody has answered yet: whether the local app will keep working at all once the cloud service is gone. Some features of a desktop app can depend on cloud services behind the scenes — authentication, model routing, workspace sync — and Conductor has not published a list of which local features depend on the cloud. That is another reason to export your data and verify your Git repositories now, while everything still works, instead of discovering a dependency in December.
What Meta Gets — and What It Might Build Next
To understand the Meta Conductor acquisition, it helps to ask what Meta is actually buying. Conductor builds no models, owns no large dataset, and has just over 100,000 users. What it has is something Meta’s AI organisation has been assembling all year: people who know how to build interfaces for multi-agent work, and a working product that proves the concept. The team joins Meta Superintelligence Labs, the division led in practice by chief AI officer Alexandr Wang, and Holtz has said he will work with Wang and product head Nat Friedman on a new interface expected in early 2027.

Why the Orchestration Layer Is the Prize
The Meta Conductor acquisition makes the most sense when you look at where AI coding is heading. The models are converging: Claude, GPT, Gemini and the open-weight frontier all write competent code now, and the differences between them are narrowing. What has not converged is the workflow around them. Running one agent is easy. Running five agents on one project — keeping their work separate, reviewing their changes, deciding which branch to merge — is still hard, and it is the problem every serious coding team hits as soon as they scale up agent use. Whoever owns the orchestration layer owns the daily habit of the developers using it.
Meta already has a coding product of its own, Muse Code, which competes directly with Claude Code and Codex. What it did not have, before the Meta Conductor acquisition, was a well-regarded multi-agent workspace. Conductor’s team brings exactly that experience in-house: workspace isolation, parallel agent supervision, diff review across agents, and the product judgement that comes from watching 100,000 developers use those features every day. Whether the result appears inside Muse Code, as a standalone Meta product, or as something entirely new in early 2027 is unknowable today — but the direction of travel is clear. In the Meta Conductor acquisition, Meta is buying the control panel, not the workers.
What Meta Has Not Said
Honesty requires listing what the Meta Conductor acquisition does not answer, because several of the questions users are asking have no answer yet. Meta has not disclosed the price. It has not said whether Conductor’s features will be incorporated into Muse Code or any existing Meta developer tool. It has not confirmed that Conductor users will be migrated to anything, or offered any migration path at all. It has not described the new interface Holtz mentioned, beyond saying something is expected in early 2027. And it has not said whether the new interface will be a coding tool, a general agent interface, or something else entirely.
That silence is normal for an acqui-hire announced four days after the Meta Conductor acquisition closed, and it is not a reason to panic — but it is a reason not to wait. If Meta eventually ships a Conductor-inspired product, you can evaluate it when it exists. Until then, your work lives in a service with a published shutdown date. Act on the dates you know, not the product you hope for.
The Same-Day Pattern: OpenAI Buys Pierre
The Meta Conductor acquisition did not happen in isolation. On the very same day, 4 November 2026, OpenAI announced it would fold Pierre’s Code Storage into Codex, and Factory absorbed HumanLayer — three coding-tool deals in twenty-four hours, with financial terms undisclosed in all three.
The pattern is hard to miss: the biggest AI labs are buying the workflow layer around coding agents as aggressively as they train the models underneath. Taken together, the two deals suggest that by 2027, the coding-agent market will be organised around a handful of large platforms, each with its own orchestration layer — and that small, independent tools will keep facing the same choice Conductor faced: get acquired, or compete against the labs that own the models.
Best Conductor Alternatives in 2026
No single tool replaces Conductor exactly, because Conductor’s value was the combination — several agents, in parallel, in one window, with review built in. The right replacement depends on which part of that combination you relied on most. If you used Conductor mainly to run Claude Code on big tasks, the answer is different from the answer for a team that ran three agents at once on one repository. Test the options below against your own repositories before you commit, and use the months the local app gives you to do it properly. For a broader comparison of AI coding assistants, see our roundup: Best AI Coding Assistant 2026.

| Tool | Parallel agents | Starting price | Best for |
|---|---|---|---|
| Claude Code | Yes, via multiple sessions and worktrees | From $20/month (Pro) | Developers who ran Claude Code inside Conductor |
| OpenAI Codex | Yes, via the Codex desktop app | From $20/month (ChatGPT Plus) | Teams already using OpenAI’s coding tools |
| Cursor | Yes, with multi-agent background runs | From $20/month (Pro) | Developers who want agents inside their editor |
| GitHub Copilot | Yes, agent mode plus coding agent tasks | From $10/month (Pro) | Teams standardised on GitHub |
| OpenCode | Yes, terminal-based sessions | Free, open source | Developers who want a free, self-hosted option |
Prices are starting prices at the time of writing; check each vendor’s current pricing before you buy.
Claude Code: The Closest Single-Agent Replacement
Most Conductor users were running Claude Code more than any other agent, so for many of them the simplest move after the Meta Conductor acquisition shutdown is to run Claude Code directly. Claude Code is Anthropic’s terminal-based coding agent, and it is the tool Conductor wrapped most often.
Used on its own, it gives you the same agent — the same model, the same capabilities — without the parallel-workspace interface. You can run several Claude Code sessions at once using Git worktrees, one per task, which reproduces the core of Conductor’s isolation model with a little more manual effort. Anthropic has also been improving long-running sessions: its message threads feature, now in public beta, cuts the wait for the first token on very long conversations by about a third, which matters when an agent has been working for an hour.
We covered that feature here: Claude Message Threads explained. The trade-off is the loss of Conductor’s visual supervision — you will be watching terminal windows instead of a workspace dashboard, and you will be doing the coordination work yourself.
OpenAI Codex: The Desktop App Option
OpenAI’s Codex now ships with a desktop app that supports parallel coding tasks, which makes it the most direct replacement for Conductor’s multi-agent workflow among the major labs’ own tools. If your team already uses OpenAI’s models, or if the Pierre acquisition — which folds Pierre’s Code Storage into Codex — appeals to you, Codex is the natural place to consolidate. The desktop app gives you a visual interface for managing several tasks at once, closer to Conductor’s experience than a terminal. The trade-off is vendor lock-in: you are running OpenAI’s agent on OpenAI’s models inside OpenAI’s app, where Conductor let you mix Claude Code, Codex and Cursor in one place.
Cursor: Agents Inside Your Editor
Cursor takes a different approach to the same problem. Rather than a separate control panel, it puts agents directly inside the code editor, with background agents that can work on tasks while you keep coding. For developers who spent most of their Conductor time reviewing diffs and approving merges, Cursor’s in-editor review flow can feel faster, because the agent’s changes appear in the same window as the code. Its multi-agent background runs cover the parallel-work case, although the experience is organised around the editor rather than around workspaces. At $20 per month for Pro, it is priced in line with the other major options.
GitHub Copilot: The Team Standard
For teams rather than individuals, GitHub Copilot is often the pragmatic replacement after the Meta Conductor acquisition shutdown. Its agent mode works inside Visual Studio Code, and its coding agent can take on GitHub issues as background tasks, which gives teams a shared, visible queue of agent work. At $10 per month for the Pro plan, it is also the cheapest of the major paid options, and for organisations already standardised on GitHub, the administrative convenience — one vendor, one bill, existing access controls — can outweigh the loss of Conductor’s workspace model. The trade-off is that Copilot’s multi-agent experience is organised around issues and pull requests rather than parallel workspaces, so the workflow feels different.
OpenCode: The Free, Open-Source Fallback
If you want to avoid depending on another venture-backed tool that could be acquired and shut down, OpenCode deserves a look. It is a free, open-source, terminal-based coding agent that runs sessions against your choice of model provider, and it was one of the agents Conductor supported. It will not give you Conductor’s visual workspace management, and you will be assembling your own parallel workflow with terminal multiplexers or worktrees — but nobody can shut it down, because there is no company to acquire. For developers who learned the vendor-risk lesson of the Meta Conductor acquisition the hard way, that independence is a feature, not a limitation.
What the Meta Conductor Acquisition Says About AI Coding
Step back from the shutdown dates, and the Meta Conductor acquisition is a useful lens on where AI coding is going — and on the risks of building a workflow on someone else’s startup. Three lessons stand out, and all three are worth carrying into whatever tool you choose next.
Lesson 1: The Orchestration Layer Is Now the Battleground
For two years, the AI coding conversation was about models: which one writes the best code, which one is cheapest, which one handles the longest context. The Meta Conductor acquisition, on the same day as OpenAI’s Pierre deal, shows the conversation has moved. The models are good enough now that the differentiator is the workflow around them — how agents are coordinated, how their work is reviewed, and how a developer supervises five agents instead of one. Meta, OpenAI and the other labs have all understood this, and they are buying the companies that solved it first. Expect more of these deals, and expect the independent orchestration tools that remain to face the same pressure Conductor did.
Lesson 2: Small Tools Can Disappear Quickly
The Meta Conductor acquisition gave Conductor’s users sixteen days between announcement and cloud shutdown, and nine days before the service went read-only. That is a short fuse by any standard, and it is a reminder that a tool’s quality is not a guarantee of its survival. Conductor was well-regarded, well-funded, and growing — and it still vanished from the cloud in under three weeks.
The practical defence is boring but effective: keep your code in Git and pushed, keep your data exportable, and prefer tools whose export story you have actually tested, not just read about. The developers who will lose work on 20 November are not the ones who ignored the news — they are the ones who assumed they had more time.
Lesson 3: Agent-Neutral Tools Are Worth Protecting
One of Conductor’s most valuable qualities was its neutrality: it let you run Claude Code, Codex, Cursor and OpenCode side by side, choosing the best agent for each task instead of the one your vendor prefers. The Meta Conductor acquisition removes one of the few neutral spaces in AI coding, and the alternatives are mostly single-vendor products.
That is not a reason to refuse them — you still need to get work done — but it is a reason to keep your workflow portable. Use Git worktrees for parallelism rather than a proprietary workspace format, keep your agent prompts and instructions in your repository rather than in a tool’s database, and make sure you can switch agents without switching your entire process. The next acquisition will come; the question is how much of your workflow survives it.
Your Data, Your Responsibility
One detail from Conductor’s announcement deserves repeating, because it is reassuring and it is the standard every tool should meet: the company said it has never sold user data or used it to train AI models, and that it will maintain that policy through the wind-down, deleting all Conductor user data when the app shuts down. That is the right behaviour, and it is worth remembering when you evaluate replacements. Check what a new tool does with your code and your conversations before you give it your repositories — not after.
Meta Conductor Acquisition FAQ
When does Conductor Cloud shut down?
Conductor Cloud becomes read-only on 13 November 2026 and shuts down on 20 November 2026, when the company begins deleting cloud user data. The dates were confirmed in Conductor’s announcement following the Meta Conductor acquisition and in its version 0.93.0 release notes. Export your data before 20 November — ideally before 13 November, while the service is still fully working.
How do I export my data from Conductor?
There are two official methods. To move a workspace to your Mac, right-click it in Conductor and select Transfer to local. To download an archive of all your account data, go to Settings, select Account, and choose Export data. Do both, and verify the results — open the archive and confirm your workspaces and chats are inside — before the 20 November deadline.
Will I get a refund for my Conductor subscription?
Conductor says active subscribers will receive refunds, and current Pro users keep their paid features at no charge until the shutdown. The company has not published a specific refund amount or processing schedule, so keep an eye on the payment method and email address tied to your account. Free users can no longer upgrade to Pro.
Does the Meta Conductor acquisition affect the local Mac app?
Not immediately. The local Mac app will keep working and will receive new model support and critical bug fixes until early 2027, when it too begins winding down. Conductor has not announced an exact shutdown date for the local app, but it has said it will delete all Conductor user data when the app shuts down. Treat the local app as a bridge to your next tool, not a permanent home.
How much did Meta pay for Conductor?
The price has not been disclosed. Meta confirmed the Meta Conductor acquisition to TechCrunch but declined to share financial details, and no source has reported a figure. Conductor previously raised a $22 million Series A round in March 2026 from Spark Capital and Matrix, but that funding figure is not the Meta Conductor acquisition price, and it should not be reported as one.
What will Meta build with the Conductor team?
We do not know yet. After the Meta Conductor acquisition, founder Charlie Holtz said the team is joining Meta Superintelligence Labs and working toward a new interface, with something expected in early 2027, alongside chief AI officer Alexandr Wang and product head Nat Friedman. Meta has not said whether Conductor’s features will appear in Muse Code, in a new product, or anywhere else — and there is no confirmed migration path for existing Conductor users.
Is my code safe if I used Conductor Cloud?
Your code is safe if it is committed and pushed to your Git remote, because Git repositories live outside Conductor. The risk is uncommitted work, unpushed branches, and agent conversations that exist only inside Conductor Cloud. Commit and push everything before 20 November, transfer your workspaces to your Mac, and download the account archive as a backup. Conductor says it has never sold or trained on user data, and that it will delete all remaining user data when the app shuts down.
What is the best Conductor alternative?
It depends on how you used Conductor. Claude Code is the closest replacement if you mostly ran Claude Code inside it; OpenAI’s Codex desktop app is the best fit if you want parallel tasks in a visual interface; Cursor suits developers who want agents inside their editor; GitHub Copilot is the pragmatic choice for teams standardised on GitHub; and OpenCode is the free, open-source option if you want a tool nobody can acquire and shut down. Test two or three against your real repositories during the months the local app keeps working.
Bottom Line: Your Checklist Before November 20
The Meta Conductor acquisition is a small deal with a short fuse. Meta gets a talented team and a proven multi-agent interface for its Superintelligence Labs; Conductor’s users get sixteen days to save their cloud work. There is no reason to panic, but there is every reason to act this week. Work through this checklist in order, and do not leave any step until the read-only week:
- Transfer your cloud workspaces to your Mac — right-click each workspace and select Transfer to local, verifying each one as you go.
- Download your full account archive — Settings, Account, Export data — and store it somewhere backed up.
- Commit and push every repository you touched through Conductor, including uncommitted changes and branches that exist only in a workspace.
- Document cloud-specific setup — environment settings, dependencies and credentials — and move secrets through a secure channel.
- Check your subscription and refund — confirm your payment method and account email are current, and watch for the refund.
- Pick your next tool and test it — Claude Code, Codex, Cursor, Copilot or OpenCode — against your real repositories while the local app still works.
- Keep the local app as a bridge, not a home — it is supported until early 2027, then it winds down too.
The broader lesson of the Meta Conductor acquisition will outlast the shutdown itself. AI coding agents are now good enough that the workflow around them matters more than the model underneath, and the companies that own the models are buying the workflows. That consolidation will continue — the same day Meta bought Conductor, OpenAI bought Pierre — and the developers who fare best will be the ones whose work lives in Git, whose data is exportable, and whose process survives whichever tool disappears next. Save your work this week. Then choose your next tool deliberately, with the vendor-risk lesson of November 2026 firmly in mind.
Sources: Conductor’s announcement of 4 November 2026 and version 0.93.0 release notes; TechCrunch’s confirmation of the Meta Conductor acquisition; Axios’s first report of the Meta Conductor acquisition; TechRepublic’s export guide and shutdown schedule; and Unite.AI’s coverage of the Meta Conductor acquisition and migration steps. The Meta Conductor acquisition price was not disclosed; where figures come from the companies themselves — such as Conductor’s reported user count and funding — they are labelled as company-reported in the text.
