Conductor Cloud becomes read-only on November 13, 2026, and shuts down on November 20. Conductor's announcement, dated November 4, says cloud workspaces stay readable and exportable after November 13, but no new messages can be sent. It also says the company begins deleting Conductor Cloud user data on November 20. If your team keeps coding-agent work in a cloud workspace, move it before the 13th, not the 20th.
The order is simple. Find the work that exists only in the workspace, move it somewhere you control, and confirm it still runs there.
We checked Conductor's announcement on November 6, 2026. The dates and export steps below come from that page.
Know the dates
- Wednesday, November 4: Conductor stopped new sign-ups and downloads. Existing free users cannot upgrade to a pro plan. Pro users keep their pro features for free.
- Friday, November 13: Cloud workspaces go read-only. You can read old chats and export data, but you cannot send new messages.
- Friday, November 20: Conductor begins deleting Cloud user data.
The announcement says the local app keeps receiving new models and critical bug fixes until early 2027, and then starts to wind down. You have time to plan the local side. You do not have time to leave Cloud work where it is.
We'll list the repositories, chats and approvals behind each cloud workspace and set up where that work runs next.
Move each workspace
Conductor gives two routes:
- 1For a workspace you still use, right-click it and choose Transfer to local. The announcement says this moves the workspace and its chats to your Mac.
- 2For everything, go to Settings, then Account, then Export data. This downloads an archive of your Conductor data.
Then work through each workspace in this order:
- 1List the workspaces and the repository behind each one. Note any changes that are not yet pushed. Those changes are the first thing to move.
- 2Transfer or export the workspace. Open the project locally and run its tests or build. A transferred chat does not prove the code still works on your machine.
- 3Push the branches you need to your git host. Write the decisions into the repository, in a short notes file or the pull request description, so they do not live only in a chat history.
- 4Store the export archive where access is controlled. Treat it as sensitive. Coding chats often hold pasted logs, config files and keys.
- 5Rotate any key, token or password that was ever pasted into a chat or a workspace environment. Deleting the chat does not undo the exposure.
- 6Delete a workspace only after you have checked its export and its pushed code.
When the move is simple, and when it is not
A throwaway experiment with no code worth keeping can be exported and left behind. A workspace that touches a client system, a payment step or customer records needs a named owner to confirm what moved, what was deleted and which credentials were rotated. Do not let that check depend on whoever happens to remember the workspace.
Where a managed setup fits
Moving files is the quick part. The harder question is how agent work should run after the move: where the code lives, who reviews agent changes, and which business tools an agent may call without a person approving the action. Where agent work touches your business systems, we set up the connections and approval steps, through custom development, MCP development and AI agents. If you are not sure what your team needs, start with a free automation audit. Describe which tools hold the work, who approves changes and what the agents are allowed to touch.
