Conductor joins Meta, deletes cloud data from November 20

Conductor, a Mac app that runs several coding agents side by side, says it is joining Meta. Its announcement sets a short clock: Conductor Cloud goes read-only on November 13, and on November 20 “we begin deleting Conductor Cloud user data.” The local app keeps working into early 2027.

If your team ran agents in Conductor’s cloud, you have about two weeks to pull the work out. The service also held your agent keys and GitHub access. Those outlive the shutdown unless you revoke them.

What Conductor announced

The news reached Hacker News at 18:22 UTC on November 4, the same day as the 0.93.0 changelog entry, which repeats the dates. From November 4, “new users can no longer sign up for Conductor or download the app,” the announcement says. Free users can’t upgrade, while “pro users can keep using pro features for free.” And “active subscribers will get a refund.”

The deal comes from Conductor’s side only. Unite.AI reports that the terms were not disclosed and quotes no Meta spokesperson; we found no statement from Meta either. Conductor says only that it has “big, crazy plans for the next interface,” expected early next year.

Why the cloud part matters more than the app

Conductor’s docs describe a tool that runs Claude Code, Codex, Cursor and OpenCode in parallel, each task on its own branch with its own terminal. The local app keeps getting “new models and critical bug fixes until early 2027.” So existing Mac users can keep working this month.

The cloud is different. Each cloud agent runs in “an isolated Linux sandbox,” and workspaces and chats are shared with the organization. The Cloud Computer holds up to 50 GitHub repositories plus environment variables and secrets “for every cloud workspace in the organization.” To set it up, a team connects the Conductor GitHub App and adds “a subscription or API key for at least one supported agent.”

Work that never left a sandbox is the risk. Files survive a sandbox’s sleep, the workspace docs say, but nothing says they survive November 20.

The dates also don’t quite line up. The announcement says deletion of cloud data begins November 20 and that “we’ll delete all Conductor user data when the app shuts down in early 2027.” We read that as two waves: the cloud now, the local app later. We would not bet a branch on the gap, though.

What to do now

1. Before November 13, finish or stop any running agent turn. After that date you can read chats and export, but not send messages.
2. Before November 20, right-click each cloud workspace and choose “Transfer to local,” or go to Settings → Account → Export data for everything. The sync runs one way, cloud to Mac. Push any branch you want to keep to GitHub as well.
3. Revoke the keys. Replace every agent API key or subscription token added to Conductor, including shared ones under Settings → Organization → Agents. Rotate the secrets your team stored under Environment; their values are hidden after saving, so check your own records for what went in.
4. Remove the GitHub App after the export. In GitHub, open Settings, then Applications, then Installed GitHub Apps, or the organization’s Third-party Access settings, and uninstall it. Also remove it under Authorized GitHub Apps.

Keep that order: export first, revoke after. The cost is real if you still use the local app, which runs until early 2027: if it uses the same key, you enter the new one there too. Questions go to support@conductor.build, the changelog says.

Sources

• Conductor: Conductor is joining Meta (announcement)
• Conductor changelog 0.93.0, November 4, 2026
• Conductor docs: overview
• Conductor docs: Cloud
• Conductor docs: Cloud Computer
• Conductor docs: Cloud getting started
• Conductor docs: Working with cloud workspaces
• Unite.AI: Conductor joins Meta and will shut down its coding-agent cloud
• GitHub Docs: Reviewing and modifying installed GitHub Apps