Skip to main content
Conductor Cloud is shutting down. This guide moves your work and your chats to Tembo, where agents also run in isolated cloud sandboxes with Claude Code, Codex, Cursor, or OpenCode.
  • November 13, 2026: Conductor Cloud goes read-only.
  • November 20, 2026: Conductor Cloud shuts down.

​
1. Save your work in Conductor

Do this before November 13 if you can.
  • Push every branch you want to keep, including new files.
  • Move your chats to your Mac. Right-click each cloud workspace and choose Transfer to local.
  • Copy your setup. Save your setup scripts, environment variable values, and gitignored files such as .env.
Using the local Conductor app? It keeps working until early 2027. Push your branches, then start at step 2.

​
2. Set up Tembo

  1. Connect GitHub. In Integrations, install GitHub and select your repositories.
  2. Add environment variables in Settings > Sandbox. See Environment variables.
  3. Create a project in Settings > Projects to replace your Cloud Computer. Select your repositories and add your setup script, replacing CONDUCTOR_* variables with paths under /workspace. Sandboxes run NixOS, so install packages with tembo.nix instead of dnf. See Projects.
To use your Claude or ChatGPT subscription, connect it in Settings > Connected accounts.

​
3. Import your chats

In the Tembo desktop app for macOS, open Settings > Import, click Import from Conductor, then click the import button, such as Import 6 chats.
The Import from Conductor dialog, listing six Conductor chats newest first, with an Import 6 chats buttonThe Import from Conductor dialog, listing six Conductor chats newest first, with an Import 6 chats button
Each chat becomes a private session titled From Conductor: followed by the chat’s title. It brings over the conversation from any Conductor agent, but not the repository, branch, or files. Running the import again doesn’t create duplicates.

​
4. Keep working

  • On a branch: comment @tembo on the branch’s pull request, such as “@tembo finish the remaining work on this branch.” See Mentioning Tembo.
  • In an imported chat: send a follow-up that names the branch. The agent, whichever you pick, gets the earlier conversation as context.
  • Routines: recreate them as agents with schedules or triggers.