Conductor joins Meta: Cloud shutdown dates and export steps

Conductor is joining Meta, and existing users have a short window to move work out of its hosted service. The immediate task is preserving projects and chats before cloud access ends, rather than waiting for details of the team’s next product.

The version 0.93.0 changelog, dated November 4, 2026, confirms the transition. The practical dates below are for the current Conductor service.

The shutdown timeline

Conductor’s announcement and FAQ distinguish three stages:

• November 4: New signups and app downloads stop. Existing free users cannot upgrade. Existing Pro users keep Pro features without charge.
• November 13: Cloud becomes read only. Old chats and exports remain accessible, but new messages cannot be sent.
• November 20: Cloud shuts down and deletion of cloud user data begins. Export before this date.

Active subscribers will receive refunds, according to Conductor. The announcement gives no processing timetable. It also does not specify a cutoff time or timezone for the shutdown, so leaving an export until the final evening creates an avoidable risk.

Transfer workspaces and keep a separate archive

The release notes describe two routes. To move a cloud workspace and its chats to a Mac, right click that workspace and select Transfer to local. For an archive of all Conductor data, open Settings → Account → Export data.

A working local copy and an independent archive serve different purposes. The first supports continued work. The second gives you a retained record to inspect if something is missing later. ByteForward recommends doing both, then checking the result before considering the migration finished.

• List the projects and conversations you still need, including archived workspaces and unfinished changes.
• Open a transferred project and confirm that its important files, branch and recent chat history are present.
• Keep the exported archive somewhere you control, and verify that the download completed and can be opened.
• Check a representative build or test workflow locally. A successful transfer alone does not establish that every dependency or local setting is ready.
• Resolve missing work while the service is still available. Keep a note of what you checked and what remains.

These are migration checks, not a report of hands on testing. ByteForward has not independently run Conductor’s transfer or export process.

Local Conductor buys time, with a limit

Local Conductor is due to receive model additions and critical fixes until early 2027, when it starts winding down. The FAQ says all Conductor user data will be deleted when the app shuts down in that period. It gives no exact local shutdown date.

For teams, that makes the local move an interim step. Use the remaining period to document how projects run outside this particular interface, who owns the repository and where essential decisions are recorded. A durable handover should still make sense to someone who cannot open the old app.

What Meta is getting, and what remains unknown

Conductor’s official product description calls it a Mac app for running coding agents in parallel. It organizes agents such as Claude Code, Codex and Cursor into isolated workspaces with separate branches and Git worktrees, followed by review and merging. That explains why chat history and unfinished branches matter alongside the source files.

The team hopes to offer something new in early 2027. No product specification or firm launch date appears in the announcement. Financial terms are not disclosed there. Existing users should plan around the published service deadlines, without assuming what a future Meta product will support.

For a separate example of how coding tools are consolidating, see our coverage of OpenAI’s planned Pierre acquisition. The customer commitments differ, so one company’s continuation promise should not be applied to another company’s service.