> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nuphos.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Migrate from Conductor Cloud

> Get your work out of Conductor Cloud before it goes read-only, then continue it with your team on Nuphos cloud computers or your own machines.

[Conductor announced](https://www.conductor.build/changelog) on November 4, 2026 that it is joining Meta and that
Conductor Cloud will shut down. Work that exists only in a cloud workspace is
not on your Mac, so save it first, then pick it up in [Nuphos](https://nuphos.ai).

> [!WARNING]
>
> **Conductor Cloud timeline**
>
> * **November 13, 2026** — Conductor Cloud goes read-only. You can still read
>   chats and export data, but you can't send messages to agents.
> * **November 20, 2026** — Conductor Cloud shuts down and Conductor begins
>   deleting cloud data.
>
> Save your work before November 13 while agents can still help you push it.

## What maps to what

| Conductor Cloud | Nuphos |
| - | - |
| Organization | [Team](https://docs.nuphos.ai/collaboration/teams.md), with Administrator, Editor, and Viewer roles |
| Cloud workspace in a Linux sandbox | An [agent](https://docs.nuphos.ai/agent/sessions.md) conversation on a **cloud computer** Nuphos runs for your team |
| Cloud Computer (shared repos, software, and setup) | A cloud computer you share with the whole team or chosen people |
| Repositories from GitHub | The [GitHub connector](https://docs.nuphos.ai/connectors/github.md), scoped to the repositories you choose |
| Shared chats, following, and **Reassign to** | Conversations are shared rooms: invite teammates and steer the same agent together |
| Local and cloud workspaces | Local, own-server, and cloud runtimes. A conversation can move between them |
| Routines | [Triggers](https://docs.nuphos.ai/agent/triggers.md): cron, webhook, and database alert |
| Open via SSH, sync to a local directory | The cloud computer's [remote desktop](https://docs.nuphos.ai/desktop.md#remote-desktops), opened from a chat's dock |
| iOS app | [Nuphos iOS app](https://apps.apple.com/app/nuphos/id6812533633) |

## 1. Save your work in Conductor Cloud

Do this for every cloud workspace you want to keep.

**1. Push every branch**

Ask the workspace's agent, or use a cloud terminal, to commit and push the
branch, including work in progress:

```bash theme={null}
git status --short
# Review the files, then stage only the paths you intend to keep.
git add <reviewed-paths>
git commit -m "WIP: move from Conductor Cloud"
git push -u origin HEAD
```

If there are no uncommitted changes, skip the add/commit steps and push
the existing branch. Review staged files for secrets before committing.
A push includes only committed files. Copy anything git ignores that you
still need, such as `.env` files or local data, somewhere safe.

**2. Or transfer the workspace to your Mac**

Right-click the workspace in Conductor and choose **Transfer to local**.
It becomes a local workspace, which you can move to Nuphos with
[Migrate from Conductor](https://docs.nuphos.ai/migrate/conductor.md). The local Conductor app keeps
working until early 2027.

**3. Export your data**

In Conductor, open **Settings → Account → Export data** and keep the
download. Nuphos cannot import Conductor Cloud chats directly, so this
export is your record of them.

**4. Write down your cloud setup**

Note the repositories, setup scripts, environment variables, and secrets
configured for your organization's Cloud Computer, and any routines. You
will recreate them in Nuphos. Copy secret values from where you originally
keep them, not from chat logs.

## 2. Set up your Nuphos team

**1. Install Nuphos and sign in**

Download the desktop app from [nuphos.ai/download](https://nuphos.ai/download)
and sign in. Nuphos creates a team for you; you are its Administrator.

**2. Connect GitHub**

Open **Connectors → Connect → GitHub** and install the Nuphos GitHub App on
the organization, choosing the repositories you used in Conductor Cloud.
See [GitHub](https://docs.nuphos.ai/connectors/github.md).

**3. Add a runtime**

Open **Runtimes → Add runtime** and choose where agents run:

* **New computer** — a cloud computer Nuphos runs for your team. Pick a
  name, a size, and who can use it: administrators, everyone, or specific
  people. Agents keep working when everyone's laptop is closed.
* **Connect your own machine** — run the one-time join command on a server
  you manage, for example in your own cloud account. See
  [Run this computer as a runtime](https://docs.nuphos.ai/cli.md#run-this-computer-as-a-runtime).

Then sign in to Claude Code, Codex, or another
[supported runtime](https://docs.nuphos.ai/agent/runtime.md#supported-runtimes) with your own
account. Model usage stays on that subscription.

**4. Prepare the computer**

Start an agent on the new runtime and have it set up your repositories,
the way your Conductor Cloud setup scripts did:

> "Clone `acme/web` and `acme/api` into `~/code`, install their
> dependencies, and run their test suites. Tell me what's missing."

Put the steps every new task needs in `CLAUDE.md` or `AGENTS.md` in the
repository, or in a [team skill](https://docs.nuphos.ai/agent/skills.md), so every agent follows
them. Create `.env` files and other secrets on the computer yourself rather
than pasting them into a chat.

**5. Invite your teammates**

In **the team’s Settings → Members**, invite people by email and pick a
role. See [Teams & members](https://docs.nuphos.ai/collaboration/teams.md) for what each role can do.

> [!NOTE]
>
> Cloud computers are billed through your team's computer plan, which an
> Administrator chooses the first time one is created. The plan counts the total vCPU of running managed computers, not a member
> allowance. See [Plans & billing](https://docs.nuphos.ai/billing.md).

## 3. Continue each branch

For each branch you pushed in step 1, start an agent on the cloud computer and
tell it where to pick up:

> "Check out branch `fix-login-redirect` of `acme/web` in a new worktree, read
> the diff against `main`, and continue: the login redirect still drops the
> `next` parameter."

If you exported a chat, attach the relevant part of it to the first message
with **+** → **Attach** so the agent has the history.

If you transferred a workspace to your Mac instead, you can keep working on
it there and later move the conversation to the cloud computer from its runtime
menu.

> [!NOTE]
>
> If the branch has an open pull request, keep pushing to the same branch so
> the pull request picks up the new commits.

## 4. Work as a team

* **Bring someone in.** @mention a teammate in a conversation and choose
  **Invite**. Everyone in the conversation sees the same tool calls and can
  steer the agent.
* **Hand work off.** Invite the teammate who takes over; the conversation and
  its history stay where they are.
* **Share a computer.** A cloud computer's access setting decides who can run
  agents on it. A teammate can also share their own machine; see
  [Share your computer with teammates](https://docs.nuphos.ai/agent/runtime.md#share-your-computer-with-teammates).
* **Share what agents learn.** [Memory](https://docs.nuphos.ai/agent/memory.md) and
  [team skills](https://docs.nuphos.ai/agent/skills.md) belong to the team, so the next agent starts
  with what the last one learned.

## 5. Recreate routines as triggers

A Conductor routine becomes a [trigger](https://docs.nuphos.ai/agent/triggers.md): a cron schedule or a
webhook, with a message template that seeds each run. For example, a nightly
dependency check becomes a cron trigger `0 2 * * *` with the message "Update
dependencies in `acme/web`, run the tests, and open a pull request if they
pass."

## FAQ

> [accordion] What happens if I miss November 13?
>
> According to Conductor's announcement, you can still read chats and export
> data until November 20, but you can't send messages to agents. After
> November 20, Conductor begins deleting cloud data.

> [accordion] Can Nuphos import my Conductor Cloud chats?
>
> Not directly. Keep the export from **Settings → Account → Export data**. If
> you transfer a workspace to your Mac and its Claude Code session appears
> under **+** → **Continue a Claude Code session**, you can continue it in
> Nuphos.

> [accordion] Do I have to use Nuphos cloud computers?
>
> No. Agents can run on a server you manage, including one in your own cloud
> account, or on a Mac running the desktop app. You can mix them in one team.

> [accordion] Who pays for the models?
>
> You do, through the account each runtime signs in with, such as your Claude
> or ChatGPT subscription. Nuphos does not resell inference.

> [accordion] Where do my secrets go?
>
> Cloud accounts and tools such as AWS, GCP, and GitHub connect as
> [connectors](https://docs.nuphos.ai/connectors/overview.md), and agents use only their authorized connections, with authentication and
> credential lifetimes depending on the provider. Application secrets,
> such as `.env` files, live on the computer where you put them.

> [accordion] Is Nuphos open source?
>
> Yes. The source is at [github.com/nuphos/nuphos](https://github.com/nuphos/nuphos),
> and you can [self-host](https://docs.nuphos.ai/self-host.md) it.

Need help moving a team? Email [hello@nuphos.com](mailto:hello@nuphos.com) or
join the [Discord](https://nuphos.ai/dc).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.