Conductor joins Meta as cloud service sets November 20 shutdown

Conductor announced on November 4 that it is joining Meta. Co-founder Charlie Holtz said the team will build a new interface with Nat Friedman and Alexandr Wang at Meta Superintelligence Labs, or MSL.

Cloud workspaces become read-only on November 13: existing chats and exports remain available, but new messages stop. The service shuts down and starts deleting cloud user data on November 20. Conductor offers workspace-and-chat transfer to a Mac and an account-wide data archive.

New sign-ups and app downloads have stopped. Existing Pro features remain free, with refunds for active subscribers.

Moving a workspace changes where the work runs

Conductor groups agent tasks with their files, conversations and code review. Its current cloud documentation describes isolated Linux environments with repositories and dependencies already installed. Agents can keep working after a laptop closes, while colleagues in the same organization can open the workspace and continue its conversation. New agent output updates live for collaborators, with presence indicators showing who has the workspace open.

Local workspaces run files and agents on the user's Mac. The company's comparison table says local processes stop when the Mac closes, while remote agents continue until their sandbox sleeps. Mac tools access local files directly.

An existing file-sync feature has a narrower purpose than transferring a workspace and its chats. It mirrors cloud files into a Mac folder in one direction; local edits do not return to the server and may be overwritten. Each member enables that sync independently. During normal sandbox sleep, files and chat history survive while processes stop; interrupted builds, servers and agent turns must be restarted after waking.

Git also preserves a different set of information from a chat archive. Local workspaces share repository history and remotes but have separate working copies. A new worktree starts with tracked files, so ignored configuration files or certificates do not automatically follow. Conductor attaches conversations, diffs and review state to the workspace around that Git checkout. Notes and handoffs can also live in a gitignored .context folder. Normal Git commits, pushes and pull requests still work from the workspace.

Local chat history lives in the Mac's Application Support directory. Cloud chats are stored on Conductor servers for synchronization and collaboration. Conductor separately collects analytics about features used, errors and model selections. Model requests go to the configured provider; integration requests go to their respective services. Those providers' data policies still apply when requests originate from a local machine.

Execution permissions follow the host environment. Conductor's security documentation says local agents can use files, terminals and tools accessible to the user's account. macOS may request permission for protected folders such as Desktop or Downloads. The permission dialog may name Conductor because it launches the process. Separating working copies organizes development tasks; operating-system permissions govern which resources the running agent can reach.

The privacy notice, updated November 3, says on-premises code and chats stay on customer systems and Conductor does not intercept or modify traffic to model providers. Optional features can still send limited chat data elsewhere: generating a session title may send its first message to an AI provider. Those features can be disabled in privacy settings. Cloud operation gives Conductor additional technical access to code, logs and chats in its managed environment.

Local Conductor starts winding down in early 2027, with new models and critical fixes supported until then.