Conductor Cloud: save your work before November 20

Protect the work your team needs

If your business product is being built with Conductor Cloud, give the transition an owner now. Ask your technical lead where the current work and conversations will be kept, and where the team will continue building.

Conductor announced on November 4 that it is joining Meta. More immediately for customers, it published a shutdown schedule for its hosted service. Conductor helps people run several AI coding assistants on a project; Cloud runs those workspaces on hosted computers.

The acquisition itself does not tell you what to buy next. The service deadlines do mean your team needs a continuation plan.

Read the announcement: Conductor: shutdown timeline, transfer instructions and refunds.

Two dates for Cloud users

On November 13, Cloud workspaces become read-only. People can still read old chats and export data, but cannot send new messages. Plan to finish the move before that date if active work depends on Cloud.

On November 20, Conductor Cloud closes and deletion of Cloud user data begins. This is the start of deletion, not a statement that every record disappears at the same moment. Save what the business needs before then.

New registrations and app downloads for new users stopped on November 4. Existing Pro users can keep using Pro features for free, and the company says active subscribers will receive refunds. Its announcement does not give a refund processing date.

Save an archive and check the workspace

Conductor gives two routes. To move a Cloud workspace and its chats to a Mac, right-click the workspace and choose Transfer to local. For an account archive, open Settings, then Account, then Export data.

Our recommendation: use the route that supports continued work and keep a separate archive for the records you need. Have the technical owner check what actually arrived before treating the move as complete.

Also confirm where the app’s source files and unfinished changes are saved. Do not assume a chat archive is a complete backup of the business product or that a transferred workspace has everything it needs to run. We have not tested the transfer.

Choose a bridge with a review date

The local Mac app has a different timeline. Conductor says it will keep receiving new models and critical fixes until early 2027, when it starts winding down. No exact final date has been given.

Existing local access may therefore provide time to assess another setup. It does not establish permanent support. Conductor has mentioned a new product for early next year without enough detail to plan a business dependency around it.

Our perspective: use this notice to secure ownership of the work and check your next development setup. Compare what the team needs to keep doing, including access, ongoing costs and the ability to move again, before choosing a replacement.

1. Today, name the person responsible for each active Cloud workspace and the work the business must retain.
2. Before November 13 where possible, transfer needed workspaces, export the account archive and check the saved contents.
3. Have the technical owner verify the app’s source and unfinished work separately, then confirm that the team can continue in the chosen setup.
4. Record any refund follow-up and review the local app’s support plan before early 2027.