Conductor, a development tool that lets users run multiple AI coding agents in parallel, officially announced on November 4, 2026 that it is joining Meta. Meta has also confirmed the acquisition to TechCrunch. As a result, Conductor's cloud service, Conductor Cloud, will shut down on November 20, and user data deletion will begin. Before that, on November 13, sending new messages will be disabled, so existing users need to migrate their work environments and save their data. Note that moving to a Mac lets you carry over workspaces and chats, but it does not preserve the same execution environment that Cloud provides.

AD

Meta acquires Conductor, a development tool for running multiple AI agents

Conductor is a development tool that lets users run and manage multiple AI coding agents in separate, independent work environments at the same time. It uses external AI agents from providers such as Anthropic and OpenAI, allowing several development tasks to proceed concurrently. Conductor does not develop its own foundation models; it has provided a development environment for making efficient use of existing AI agents.

Conductor launched its product in July 2025, and the company was founded in 2024. According to Axios, Charlie Holtz is CEO and Jackson de Campos is CTO. Axios reported the acquisition based on information from people familiar with the deal, and financial terms have not been disclosed. Conductor has announced it is joining Meta, and TechCrunch has also confirmed the acquisition with Meta.

New messages stop November 13; Cloud shuts down and data deletion begins November 20

Starting November 4, the day the acquisition was announced, Conductor stopped new user sign-ups and app downloads. Existing free users can no longer upgrade to the paid Pro plan, while users already on Pro can keep using Pro features free of charge until the service ends. The company has also indicated it will issue refunds for active subscriptions.

The two key dates for Conductor Cloud users are November 13 and November 20. After November 13, you will no longer be able to send new messages in Cloud, but you can still view past chats and export your data. On November 20, Cloud will shut down and user data deletion will begin. Note, however, that November 20 is the day deletion starts, not the day all data has been deleted.

What users need to do depends on whether they want to migrate their work environment or preserve their records.

Goal Deadline / condition Required action Caveat
Continue working Cloud stops accepting new messages on November 13 Right-click the workspace and select "Transfer to local" to move it to your Mac Workspaces and chats can be migrated, but the execution conditions will not be the same as in Cloud
Save your records Data deletion begins November 20 Export all data via "Settings → Account → Export data" Restoring the data elsewhere or automatic migration to a successor product is not guaranteed
Keep processes running after the app is closed Previous conditions cannot be maintained after Cloud ends A change in execution environment is required In the local version, sessions end when the app is quit or the Mac is shut down

The key point is that migrating to a Mac and exporting all your data are separate operations. "Transfer to local" moves workspaces and chats to your Mac so you can keep working, but it does not guarantee that all data is preserved. "Export data," meanwhile, is for saving your records, and it is not stated that exported data can be restored as-is in another environment. If you want to keep both your work environment and your past records, you need to do both.

AD

Background execution is lost when moving to a Mac

The biggest difference between Conductor Cloud and the local version is where the AI agents run. According to Conductor's FAQ, in Cloud, agents run in a Vercel sandbox, so processing can continue even after you close the Conductor app. In the local version, by contrast, processing runs on your Mac, and the session ends if you quit the app or shut down the Mac. So even if you migrate a workspace, you cannot keep working the old way, letting AI agents make progress while the app is closed.

Data storage also differs. In Cloud, chat history is stored on Conductor's servers, whereas in the local version, session data is stored on your Mac. The FAQ also explains that messages from the local version are sent directly to the model providers. In other words, moving to the local version reduces your dependence on Conductor's cloud environment, but it does not eliminate communication with AI models, and it does not make the tool fully offline.

This difference may affect the workflow of users who hand long-running development tasks to multiple AI agents. In Cloud, work could continue while you were away from your Mac, but with the local version, the app and the Mac must stay running. When considering migration, check not only whether your workspaces and chats carry over, but also whether you can reproduce your existing workflow in a local environment.

Local version to be updated through early 2027; successor product details undecided

Conductor says it plans to keep supporting new AI models and fixing critical bugs in the local version through early 2027. It has also indicated it hopes to offer new products or services around that time, but specifics such as product names, features, pricing, and migration terms for existing users have not been disclosed. Note too that early 2027 refers to the planned update support period; it does not mean the app will be forcibly disabled at that point. At the same time, there is no guarantee it can be used indefinitely beyond that.

Attention is also turning to how Meta will use Conductor's technology and development team after the acquisition. However, details of a successor product have not been made public, and it is unclear whether existing Conductor users will be migrated to any new service automatically. It is therefore best not to postpone migration in the expectation that a successor will arrive.

The most pressing issues for existing users are the end of new message sending on November 13 and the start of data deletion on November 20. Confirm both the migration to a Mac to continue working and the export of all data to keep your records, and review whether you depend on the background execution you used in Cloud. New developments under Meta will have to wait for future announcements, but it is important to secure your current work environment and data before Cloud ends.