Moving from Conductor Cloud
Updated
Conductor Cloud goes read-only on November 13, 2026 and shuts down on November 20. Save your cloud workspaces, then run Claude Code, Codex, or Cursor in a git worktree each on a Prized box that keeps working with your laptop closed.
On this page11
Conductor Cloud goes read-only on November 13, 2026 and shuts down on November 20, when Conductor begins deleting Cloud data; the local Mac app keeps getting new models and critical bug fixes until early 2027, when it starts winding down (Conductor's notice). A Prized box is a cloud Linux machine that keeps its disk, with Claude Code and Codex installed. Each agent gets its own git worktree and tmux session on it, as each got a cloud workspace in Conductor, and keeps working with your laptop closed.
1. Save your cloud work before November 13
From November 13 you can still read old chats and export data, but you can't send new messages; active subscribers get a refund.
- Code: commit and push each cloud workspace's branch, or right-click the workspace in the Mac app and choose Transfer to local to move it and its chats to your Mac.
- Chats and settings: Settings → Account → Export data downloads all your Conductor data.
- Cloud Computer: copy its install script and each repository's setup script from your organization settings. Conductor hides saved environment variable values there but sets them in every cloud workspace, so read the ones you need in a cloud workspace's terminal, or take them from wherever you keep them; on Prized they go in Variables on the box page's Settings tab, and API keys in Secrets.
2. Get a box
Sign up at prized.dev: the tour starts a box on $30 of free credit with no card, then shows one command that installs the CLI and signs this machine in (Quickstart). Run it from your home folder, so it doesn't copy the repo that step 3 clones.
3. Put your repo on the box
In your main clone of the repo on your Mac, on its default branch:
prized setup . --clone--clone needs the repo pushed to a remote named origin; for a repo you haven't pushed, prized setup . copies it instead.
Setup clones the repo's origin to ~/code/<folder> on the box, named for this folder in lowercase and with all its branches, and signs your coding agents in there; the steps below call it myproject. A private repo clones with your Mac's GitHub CLI sign-in if you let setup bring it (Sync), and setup offers to install the Node.js your Mac has, since a fresh box has none (Machines). When it offers to open an agent on the box, answer n for now; step 5 starts one per worktree.
Then save your Cloud Computer's install script as install.sh, point its paths at ~/code/myproject, and run it once from your home folder. The box keeps what it installs, and it is Ubuntu 24.04, so dnf install lines become apt-get install (package names can differ); pnpm and Git LFS are not on a fresh box either.
prized cp install.sh :install.sh
prized exec -- bash install.sh4. Add a worktree per task
prized sshThen, on the box:
cd ~/code/myproject
git worktree add ../myproject-auth auth
git worktree add ../myproject-billing -b billingThe first checks out a branch you pushed from Conductor; -b starts a new one. A worktree holds tracked files only, so run your repository's setup script in it, the step Conductor ran for each new workspace.
5. Start an agent in each
prized agents run claude --session claude-auth --dir code/myproject-auth -- --permission-mode auto "add rate limiting to the login endpoint"
prized agents run codex --session codex-billing --dir code/myproject-billing -- --sandbox workspace-write --ask-for-approval neverStart each agent in a mode that doesn't stop to ask: a question waits until you come back, with the laptop closed too, and accept-edits mode still asks before most commands. For Claude Code that's auto mode, passed on its command line as above, since auto set in the repo's .claude/settings.json doesn't take effect; after 3 blocked actions in a row it goes back to asking (Permission modes). For Codex, the workspace-write sandbox with approvals set to never keeps its sandbox and never asks (Run Codex in the cloud).
Everything after -- goes to the agent, so Claude Code starts on the task in quotes with no need to attach. To give an agent its task by hand, attach with prized ssh -s codex-billing, and detach with Ctrl-b, then d. OpenCode installs on first use (prized agents run opencode), and setup's --install-cursor, with --agent cursor, installs the Cursor CLI (Agents). Give each dev server its own port, such as 3001 and 3002 (Ports).
6. Watch them, then close the laptop
prized ssh --ls lists the sessions, and prized ssh -s codex-billing opens one. The agents run in tmux on the box, so closing the laptop ends only the connection. From your phone, open the box's terminal on the dashboard with ?session=claude-auth added to its address (Terminal).
On the free credit, a box pauses after 2 hours with nothing using it. An agent printing in its session counts as use, but a long wait for your answer can still pause it; prized box auto-pause mango off, with your box's name for mango, keeps it up, and it then bills while idle (Auto-pause).
7. Review and merge
If the agent hasn't committed, commit in its worktree, then push and open the pull request:
git add -A
git commit -m "Add rate limiting to the login endpoint"
git push -u origin auth
gh pr creategh on the box is signed in if it was on your Mac at setup. Once merged, git worktree remove ../myproject-auth cleans up (Parallel agents).
What Conductor Cloud did, on Prized
| In Conductor Cloud | On Prized |
|---|---|
| A cloud workspace per agent | A git worktree and tmux session per agent on one box; or a box per agent, forked from one you set up, which needs a plan (A box per agent) |
| Cloud Computer: repositories, install and setup scripts, environment variables and secrets, builds | An environment: repos to clone, a setup script, env vars, and secret files, saved as versions that boxes you create from the CLI or API start from |
| Agents keep working after your Mac closes | The same, in tmux on the box, with no maximum run time; the box keeps its disk while paused |
| Claude Code, Codex, and Cursor, with your subscriptions or API keys | All three run on the box, and OpenCode too; setup copies your Claude Code sign-in over, and a Codex ChatGPT sign-in is made fresh on the box (Credentials) |
| Open via SSH, Remote SSH editors | prized ssh, or any editor that opens an SSH host (Cursor or VS Code) |
| Sync to a local directory, cloud to Mac | Sync, both ways, .git included |
| Forward ports | Nothing to declare: ports 3000 to 9999 on the box open on your Mac's localhost; prized ports share 3000 makes a link for your workspace's members (Ports) |
| The iPhone app | The box's browser terminal on your phone, or Claude Code's Remote Control in the Claude app (From your phone) |
| The Conductor API | The API: create a box, send its agent a prompt, and follow the run; prized prompt does the same from a terminal or a script (Prompt an agent remotely) |
A sandbox per task
To give each task a fresh machine that is deleted when it ends, have one orchestrator agent on your box start a sandbox per task (Run an orchestrator agent with a sandbox per task).
What's different
- No Conductor app: you work in a terminal, your editor over SSH, or herdr, not in Conductor's chat and diff views.
- Multiplayer: owners and members of a Prized workspace can open any box in it, its terminal included, and Activity on the dashboard lists each box's owner, sessions, and last prompt (Team activity). There are no shared chats with presence, following, or reassigning.
- Chats: your Conductor chats don't carry over, so keep the export. Put what an agent should know in a
CLAUDE.mdorAGENTS.mdin the repo. - Billing: a box bills for the time it is awake, and only for its disk while paused (Billing).
Getting help moving
Email with what your Cloud Computer ran, and we will help you map it.