Meta acquires Conductor: export your agent workspaces by Nov 20

Meta has acquired Conductor, the Mac app that runs parallel coding agents, and the shutdown clock is already running. TechCrunch reports that Meta confirmed the deal on November 4 and gave no other details. Conductor's own notice sets the dates: new sign-ups stopped the same day, Conductor Cloud goes read-only on November 13, and cloud user data starts to be deleted on November 20. If your team runs agents there, you have about two weeks.

What actually happened

Conductor lets one engineer start several Claude Code, Codex and Cursor agents, each in an isolated workspace, then review and merge what they produce. Charlie Holtz and Jackson de Campos founded it in 2024, and it raised a $22M Series A from Spark and Matrix in March, per SiliconANGLE. Terms were not disclosed.

The wind-down, from Conductor's announcement:

• November 4: no new sign-ups or downloads. Existing pro users keep pro features for free.
• November 13: Conductor Cloud goes read-only. You can read old chats and export, but you cannot send new messages. Active subscribers get a refund.
• November 20: Conductor Cloud shuts down and deletion of cloud user data begins.
• Early 2027: the local Mac app gets model updates and critical fixes until then, then winds down. Conductor says it will delete all user data at that point.

To get out, Conductor says to right-click a cloud workspace and choose Transfer to local, or use Settings → Account → Export data for a full archive.

Why it matters for your coding agent stack

This is the second coding-tool acquisition announced on November 4. The other was OpenAI and Pierre. Pierre customers got a continuity promise. Conductor customers got 16 days.

The code itself is mostly safe. Conductor worked on top of your Git repo, and the agents ran on your own Claude, OpenAI or Cursor accounts. The part at risk is the layer the tool owned: chat history, agent reasoning, half-finished branches in cloud sandboxes, and the workflow your team built around one orchestrator. That layer is exactly the part nobody backs up.

We do not think the answer is "never use a startup tool." Use them, but keep these rules:

• Push every agent branch to your own remote. If work only exists in a vendor sandbox, it is not your work yet.
• Keep the orchestrator thin. The model accounts, the repo and the CI pipeline should belong to you. The orchestrator should be the part you can swap in an afternoon.
• Export on a schedule, not on the deadline. If a tool has an export button, run it monthly.

Sources: Conductor, "Conductor is joining Meta", TechCrunch, SiliconANGLE.