Migrate from Conductor Cloud

Conductor is joining Meta, and Conductor Cloud is shutting down. This guide gets your cloud work out of Conductor and into Codz, either on your Mac or in Codz Cloud.

For the local Conductor app, see Migrate from Conductor.

What maps to what

1. Save your work in Conductor

Do this first, before November 13 if you can.

1. Push every branch. In each Conductor Cloud workspace, commit all changes, new files included (git add -A), and push the branch. A pushed branch is safe on GitHub whatever you choose next.
2. Copy out ignored files. A push leaves out Git-ignored files, such as .env files and local data. Copy any you need before November 20.
3. Export your data. In Conductor, go to Settings ▸ Account ▸ Export data for a copy of your chats. Conductor Cloud’s chats don’t come over to Codz, so this export is your record of them.

Then choose where to continue: on your Mac, or in Codz Cloud.

2a. Continue on your Mac

1. In Conductor, right-click the cloud workspace and choose Transfer to local. Conductor moves the workspace and its chats to your Mac.
2. Follow Migrate from Conductor to open the workspace in Codz and convert your scripts. A transferred chat that the agent’s CLI saved is listed in Codz’s sidebar, ready to continue.

If you only pushed the branch, open the repository in Codz, then in the Git panel (⌘⇧2) click the branch and choose Check Out as Local Branch on the pushed branch. Start a chat there, or one in a new worktree from that branch.

2b. Continue in Codz Cloud

A Codz Cloud chat runs its agent on a Linux machine, so it keeps working when your Mac sleeps or is closed. Cloud needs Codz Pro, Max or a team seat, and a Codz account signed in on your Mac. See Plans & pricing.

Codz Cloud gets your code from your Mac, not from GitHub: when a Cloud chat starts, the Mac sends the repository’s history and your uncommitted changes. So start from a checkout of the repository on your Mac.

Connect your agents for Cloud

Cloud chats don’t use the logins your Mac’s agent CLIs keep. In codz.com/app, open Settings ▸ Models & providers and connect the accounts you want Cloud chats to use. Claude needs an Anthropic API key there, and Codex an OpenAI API key.

Ollama and local models run only on your Mac. A provider Cloud doesn’t offer yet says so in the composer’s Cloud entry.

Add your setup

When a Cloud machine prepares a chat’s checkout, it reads .codz/environment.json from the repository: the install command it runs, a start command, and the environment variables and secrets the project needs. A Conductor Cloud setup like this:

{
  "scripts": {
    "setup": "bun install",
    "run": "bun dev"
  }
}

becomes:

{
  "schemaVersion": 1,
  "installCommand": "bun install",
  "startCommand": "bun dev",
  "variables": { "NODE_ENV": "development" },
  "secrets": { "DATABASE_URL": "database-url" }
}

• variables are plain values, committed with the repository. Up to 64 variables and secrets in all.
• secrets map a variable name to a secret’s ID. Save each value first in codz.com/app under Settings ▸ Machine setup ▸ Environment secrets, with Secret ID and Secret value. Values are encrypted and never shown again; the file holds only the ID.
• Without the file, Cloud picks an install command from your lockfile: package-lock.json, pnpm-lock.yaml, a classic yarn.lock, uv.lock, requirements.txt, Gemfile.lock or go.mod.
• Nothing is read from .env files. Put what a Cloud chat needs in variables or secrets.

Commit and push .codz/environment.json to every branch you start Cloud chats from. If setup fails, the chat says so and carries on without it.

CONDUCTOR_PORT isn’t set in Conductor Cloud, so cloud scripts rarely need a port change.

Continue each branch

1. On your Mac, check out the branch you pushed from Conductor (see 2a).
2. Press ⌘N, pick the project, and in the composer’s destination menu, under Run on, choose Cloud: “Runs on Linux in Codz Cloud. It keeps working while this Mac sleeps.”
3. The chip reads From and your branch: Cloud starts from it. Tell the agent where to pick up, for example “Continue the work on this branch. Read the last commits and the open PR first,” and send.

The branch chip’s Copy Cloud branch copies the branch the chat works on. If it isn’t the branch your Conductor pull request came from, open a new pull request from it, or merge it into the old branch.

To move a chat you already started on your Mac, choose Chat ▸ Move to Cloud…. It takes the conversation and your uncommitted changes, untracked files included, and keeps working there while your Mac sleeps. Ignored files and .env files stay behind. Chat ▸ Bring Back from Cloud returns it to your Mac.

Move your routines

Codz’s scheduled runs happen on your Mac. In a chat, choose Chat options ▸ Schedule task… and pick Once, Daily, Weekdays or Weekly. Schedules run in Ask or Plan, while Codz is open and the Mac is awake. See Schedules.

3. Check your usage

Codz Cloud is metered in Cloud minutes: Pro includes 50,000 a month and Max 600,000. A machine counts while it is awake, idle or not, and it goes to sleep after about ten minutes with no running work, no open app and no attached terminal. It wakes when you send. Past your minutes, extra time is $0.03 per Linux machine-hour from prepaid credit. See Cloud minutes and credit.

Get help

Stuck on a step? See Troubleshooting.