Comparison

Conductor Cloud is shutting down: keep your agents running on your own machine

Conductor is joining Meta. Conductor Cloud goes read-only on 13 November 2026 and shuts down on 20 November 2026, when deletion of Cloud user data begins. The local Mac app keeps working for now, with updates until early 2027, when it starts winding down. If you used Cloud so that Claude Code or Codex kept working after you closed your laptop, this page covers what Conductor recommends and one way to keep that on a machine you already own.

Verified 2026-11-12 Every Conductor claim below was checked against Conductor's own announcement, changelog, homepage and docs — listed under Sources.

The short answer

First, export your work: in Conductor, right-click a cloud workspace and choose Transfer to local, or use Settings → Account → Export data, before 20 November. Then, if you still want agents that outlive your laptop, run Claude Code or Codex on a machine that stays on, such as a home server, VPS, NAS, Mac mini or GPU box, and use AI Commander to start them there as detached jobs from the AI client you already use. AI Commander does not replace Conductor's workspace app; it gives your AI client hands on that always-on machine.

The Conductor timeline

What Conductor Cloud did

In Conductor's words, Cloud "runs every agent in its own isolated cloud sandbox, with your repos and dependencies pre-installed", and "agents keep working after you close your laptop". Cloud workspaces ran in Vercel sandboxes in the us-east-1 region, were shared with your organization, and could be opened over SSH or synced to a local folder. A workspace slept after 20 minutes without agent or terminal activity, and every sandbox stopped at a maximum lifetime of 23 hours and 50 minutes. Local workspaces, by contrast, run on your Mac, and "if you close the app or shut down your Mac, those sessions end."

What AI Commander is

A hosted relay plus a small agent per machine, reachable as an MCP server and as a plain REST API. It brings no model and no chat window: the AI client you already use — Claude, ChatGPT, Codex, Grok or any MCP client — is the interface, and AI Commander is the hands on your machines. The agent holds one outbound WebSocket open, so there is no inbound port, no exposed SSH and no VPN, and it runs on macOS, Windows and Linux. Detached jobs (remote_job_start, _status, _logs, _cancel) outlive the call and the conversation. One of the things you can start that way is Claude Code or Codex itself — see remote coding agents and Claude Code on a VPS without SSH.

Side by side

AI CommanderConductor Cloud
Status Available; Free plan up to 10 saved machines Read-only from 13 November 2026, shut down on 20 November 2026
Where agents run On your own computers: macOS, Windows or Linux, desktops, servers, NAS and GPU boxes Isolated Linux sandboxes (Vercel, us-east-1)
Keeps working after your laptop closes ✓ When the job runs on a machine that stays on; detached jobs with start / status / logs / cancel by job id ✓ "Agents keep running until the sandbox sleeps"
Run time limits A single command is capped at 1 hour; a detached job keeps running after the call returns Sleep after 20 minutes without agent or terminal activity; maximum sandbox lifetime 23 hours 50 minutes
Parallel isolated workspaces, diff review, PR flow ✗ No workspace app; use your AI client and your own git workflow ✓ Chat, diff, git, terminal and pull request workflow
Team sharing of workspaces ✗ ✓ Workspaces and chats shared with your organization
Session data Command text and output pass through the relay's memory and are not written to logs or a database "chat messages from cloud workspaces are stored on Conductor's servers"
Connection direction ✓ Agent dials out over one WebSocket; no inbound port, no SSH, no VPN not applicable: the sandboxes are hosted; SSH and file sync are offered for access

We read the sources listed below on 2026-11-12. We make no claims about Conductor's plans beyond what its own announcement says, and none about the other product's security or reliability.

Moving to an always-on machine with AI Commander

  1. Export from Conductor first. Transfer to local or Settings → Account → Export data, before 20 November.
  2. Pick a machine that stays on — a home server, a VPS, a NAS, a Mac mini or a GPU box — and put your repository there with git clone.
  3. Install the AI Commander agent on that machine and sign Claude Code or Codex in there with your own subscription.
  4. Connect your AI client (Claude, ChatGPT, Codex, Grok or any MCP client) — see Connect.
  5. Start the agent as a detached job and close the laptop. Later, from any chat, ask for the job's status or logs by its id.

When NOT to use AI Commander

Look elsewhere if: Conductor's announcement →

FAQ

What is happening to Conductor Cloud?
Conductor announced on 4 November 2026 that it is joining Meta. Per its own announcement, checked 2026-11-12: from 4 November new users could no longer sign up or download the app, Conductor Cloud workspaces go read-only on Friday 13 November (you can read old chats and export data, but not send new messages), and on Friday 20 November Conductor Cloud shuts down and Conductor begins deleting Cloud user data. Local Conductor keeps working for now, with new models and critical bug fixes until early 2027, when it starts winding down.
How do I move my Conductor Cloud work before it shuts down?
Conductor's own instructions: right-click a cloud workspace and choose Transfer to local to move it and its chats to your Mac, or go to Settings, Account, Export data to download all your data. Do this before 20 November 2026.
Is AI Commander a replacement for Conductor?
No. Conductor is a Mac app for running parallel Claude Code, Codex and Cursor agents in isolated workspaces and reviewing their diffs. AI Commander has no workspace app, diff view or isolated sandboxes. It covers one thing Cloud users relied on: agents that keep working after your laptop closes. It does that on a machine you own instead of a hosted sandbox.
Can Claude Code or Codex keep running after my Mac closes without a cloud sandbox?
Yes, if they run on another machine that stays on, such as a home server, a VPS, a NAS, a Mac mini or a GPU box. Install the AI Commander agent there, connect the AI client you already use, and start Claude Code, Codex or any long command as a detached job. It keeps running after the chat ends, and you check status or logs by job id from a new chat.
Do I keep using my own Claude or Codex subscription?
Yes. AI Commander supplies no model. Claude Code or Codex runs on your machine with your own login, and AI Commander lets your AI client start it there and check on the job later.

Sources & verification

Conductor facts on this page were read from its own site on 2026-11-12:

AI Commander facts trace to llms.txt, the docs, the privacy policy and the pricing page.

Let Claude Code and Codex work on the machines you already have

Install the agent on a PC, a Mac, a server or a GPU box and connect Claude, ChatGPT, Codex or Grok. Free for up to 10 machines.