Conductor Cloud users have two November deadlines for preserving their AI coding work. The company’s November 4, 2026 release says hosted workspaces will become read-only on November 13 and shut down on November 20, as Conductor joins Meta.
Conductor organizes coding agents, project files and conversations. For developers and teams with unfinished work stored in Cloud, the immediate task is to preserve those records and establish where work will continue.
Separate the working deadline from the export deadline
The official shutdown notice sets out two stages:
November 13: Cloud becomes read-only. Existing chats remain readable and data export remains available, but users cannot send new messages.
November 20: Cloud shuts down. Conductor says it will begin deleting Cloud user data that day and asks users to export beforehand.
For continuity, aim to move active work before November 13. Treat the following week as time to recover records, not extra time to keep prompting agents. Neither notice specifies a cutoff hour or timezone, so do not plan around a last-minute download.
1. Identify the work to keep
Use your existing Mac installation. New sign-ups and downloads closed on November 4; the desktop documentation lists macOS support, not Windows or Linux.
Include team-owned and archived work, not just the projects pinned in your sidebar. Conductor’s collaboration guide describes Home filters for people, projects and archived workspaces. Agree who will retain each shared project and its conversations, and who needs access afterward.
2. Transfer workspaces, then save an archive
Follow the documented workspace-transfer action and keep a separate account export:
Right-click a Cloud workspace you need to continue and choose Transfer to local. Conductor says this moves the workspace and its chats to your Mac.
Open Settings → Account → Export data to download the data archive. Save it separately from the working project and check that the download is present and readable.
Do not substitute Sync to a local directory for migration. The file-sync documentation describes a one-way Cloud-to-Mac mirror: local edits do not travel back and may be overwritten. Sync is also per person, so one teammate’s local folder does not establish that everyone has preserved their work.
The migration instructions do not specify the export format, import compatibility with other products, or an itemized list of everything transferred. A downloaded archive should not be treated as a ready-to-use replacement workspace. If the controls are missing or a transfer is blocked, use the support contact in the release notice; it does not specify a minimum app version.
3. Verify that the project works on the Mac
Files and chats are only part of a working project. Conductor’s Cloud Computer documentation describes organization-level software, repositories and environment settings. Its setup documentation also distinguishes Cloud setup scripts from local ones: local workspaces use scripts.setup in .conductor/settings.toml, or the legacy conductor.json.
Before relying on the local copy, have the responsible developer check:
Project state: inspect the expected files, current branch, unfinished edits and any files not yet tracked in Git. Keep an independent backup of important code and unfinished changes.
Conversation records: open the chats you need and inspect the saved archive. Do not infer completeness from seeing a project folder.
Dependencies and access: compare required software and environment-setting names with the Cloud setup. Configure needed credentials through your normal protected process, without printing them into chats or logs.
Usability: run the project’s usual tests or build locally and check how teammates will access the work. The migration notice does not promise equivalent shared access on a Mac.
Review permissions before resuming agent work. The security documentation says local agents operate with your user account’s access, while model requests go directly from the Mac to the configured provider. Moving locally does not, by itself, make the workflow offline.
4. Decide whether local operation meets your needs
The main operational tradeoff is computer availability. According to the Cloud FAQ, hosted agents can continue after the app closes. Local sessions end when you close Conductor or shut down the Mac. Preserving a conversation is not the same as preserving unattended execution.
If remote team execution is essential, assess that separately from saving your records. Our guide to Copilot-funded cloud tasks in JetBrains Air explains access and billing considerations for another hosted workflow. Do not assume it can import Conductor work.
App access and model costs are separate, too. The shutdown notice says existing Pro users retain Pro features free and active subscribers will receive refunds, without specifying amounts or processing dates. Conductor’s billing explanation says model usage is billed through the provider account or API arrangement. Free app features do not make model usage free.
Treat local Conductor as a temporary bridge. The release notice promises model additions and critical fixes until early 2027, not indefinite support. No precise final date or successor migration path is specified. Preserve the work now; do not make its survival depend on the planned future product.