> ## 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

> Move your repositories, worktrees, scripts, and Claude Code or Codex sessions from the Conductor Mac app to Nuphos.

[Conductor announced](https://www.conductor.build/changelog) on November 4, 2026 that it is joining Meta. The local
Conductor app keeps receiving new models and critical fixes until early 2027,
so there is no rush to move work that lives on your Mac. This guide shows how
to bring that work into [Nuphos](https://nuphos.ai) when you are ready.

> [!WARNING]
>
> **Using Conductor Cloud?** Cloud workspaces go read-only on **November 13,
> 2026** and Conductor starts deleting cloud data on **November 20, 2026**.
> Follow [Migrate from Conductor Cloud](https://docs.nuphos.ai/migrate/conductor-cloud.md) first.

## How the two fit together

Conductor and Nuphos solve different parts of the same problem. Conductor gives
each task its own git worktree on your Mac. Nuphos runs the coding agent you
already use, such as Claude Code or Codex, in a conversation your team can join,
on your Mac, on your own server, or on a cloud computer Nuphos manages. Your
code stays in git, so moving is mostly a matter of pointing an agent at the
same folders.

| Conductor | Nuphos |
| - | - |
| Mac app | [Desktop app](https://docs.nuphos.ai/desktop.md) for macOS, Windows, and Linux, plus the [iOS app](https://apps.apple.com/app/nuphos/id6812533633) |
| Agents (Claude Code, Codex, and others) | [Runtimes](https://docs.nuphos.ai/agent/runtime.md): Claude Code, Codex, OpenCode, Grok Build, and Antigravity, each signed in with your own account |
| Workspace (one task, one branch, one worktree) | An [agent](https://docs.nuphos.ai/agent/sessions.md) conversation. Nuphos does not create worktrees for you; the agent works in whichever folder or worktree you point it at |
| Repository added in the app | A folder on the computer the agent runs on, or a GitHub repository shared through the [GitHub connector](https://docs.nuphos.ai/connectors/github.md) |
| Several workspaces side by side | Several agents side by side; split the window with **⌘D** or **⌘⇧D** |
| `conductor.json` or `.conductor/settings.toml` scripts | No per-repo config file. Keep scripts in the repo and tell the agent when to run them, or store the steps as a [team skill](https://docs.nuphos.ai/agent/skills.md) |
| `CONDUCTOR_*` environment variables | Not set. Use git and plain paths instead (see [Convert your scripts](#3-convert-your-scripts)) |
| Diff viewer and checks | Pull requests, commits, and workflow runs in the [GitHub connector](https://docs.nuphos.ai/connectors/github.md) |
| Claude Code chats in `~/.claude` | **Continue a Claude Code session** in the composer imports them into a Nuphos conversation |
| Single user | A [team](https://docs.nuphos.ai/collaboration/teams.md): invite teammates into a conversation and steer the same agent together |

## 1. Install Nuphos and add a local runtime

**1. Install the desktop app**

Download Nuphos from [nuphos.ai/download](https://nuphos.ai/download) and
sign in. Nuphos creates a team for you the first time.

**2. Use the Claude Code or Codex already on your Mac**

Open **Settings → This computer → Local runtime**. Nuphos detects the
Claude Code, Codex, OpenCode, or Grok Build CLI installed on the computer
and signs it in with your own account. Inference keeps running on your
existing subscription; see [Plans & billing](https://docs.nuphos.ai/billing.md).

**3. Start an agent**

Choose **New agent** in the sidebar and pick the local runtime in the
composer.

A local runtime runs only while Nuphos is open. To keep agents working after you
close the laptop, add a cloud computer or your own server under **Runtimes**.
See [Runtimes and computers](https://docs.nuphos.ai/agent/runtime.md).

## 2. Keep working in your existing worktrees

Conductor creates each workspace as a git worktree, usually under
`~/conductor/workspaces/<repo>/<workspace>`. A worktree is an ordinary git
checkout, so nothing needs to be exported. List them from the original
repository:

```bash theme={null}
git worktree list
```

A local runtime runs on your Mac as you, so an agent can work in any of these
folders. Start one agent per workspace and name the folder in your first
message:

> "Work in `~/conductor/workspaces/web/warsaw`. It is on branch
> `fix-login-redirect`. Read the diff against `main` and continue the task."

The local runtime also has its own **Workspace folder**, shown under
**Settings → This computer → Local runtime**. Agents start there when you don't
name a folder.

> [!TIP]
>
> If you want your worktrees outside `~/conductor` before you uninstall
> Conductor, move them with git so the repository keeps track of them:
> `git worktree move ~/conductor/workspaces/web/warsaw ~/code/web-warsaw`.

For a new task, ask the agent to create the worktree it needs, for example
"create a worktree for a new branch `add-billing-export` off `origin/main` and
work there". Nuphos does not manage worktrees itself, so the agent uses
`git worktree` like you would.

> [!WARNING]
>
> Don't archive a workspace in Conductor until its branch is pushed or you have
> moved the worktree. Archiving runs your archive script and ends the workspace
> in Conductor.

## 3. Convert your scripts

Conductor reads setup, run, and archive scripts from `.conductor/settings.toml`
or the older `conductor.json`. Nuphos has no equivalent file and does not run
scripts on its own when a conversation starts. Move the commands into files the
repo already owns, and tell the agent when to run them.

A typical `conductor.json`:

```json conductor.json theme={null}
{
  "scripts": {
    "setup": "pnpm install && cp \"$CONDUCTOR_ROOT_PATH/.env\" .env",
    "run": "pnpm dev --port $CONDUCTOR_PORT",
    "archive": "./scripts/archive.sh"
  },
  "runScriptMode": "nonconcurrent"
}
```

becomes a script in the repo:

```bash scripts/setup.sh theme={null}
#!/usr/bin/env bash
set -euo pipefail
pnpm install
# The main checkout is the first entry in `git worktree list`.
root="$(git worktree list --porcelain | sed -n 's/^worktree //p' | head -n 1)"
[ -f .env ] || cp "$root/.env" .env
```

and a note the agent reads. Claude Code reads `CLAUDE.md` and Codex reads
`AGENTS.md` from the repository on its own:

```markdown CLAUDE.md theme={null}
## Working in a new worktree
- Run `scripts/setup.sh` once before anything else.
- Start the dev server with `pnpm dev --port <port>`. Pick a free port and
  tell me which one you used.
- Before deleting a worktree, run `scripts/archive.sh`.
```

What changes:

* **`CONDUCTOR_ROOT_PATH`** — use the first entry of `git worktree list`, as
  above, or an absolute path.
* **`CONDUCTOR_WORKSPACE_PATH`** — the current directory, or
  `git rev-parse --show-toplevel`.
* **`CONDUCTOR_WORKSPACE_NAME`** — the folder name, `basename "$PWD"`, or the
  branch name, `git branch --show-current`.
* **`CONDUCTOR_PORT`** — Nuphos does not assign ports. Pass a port explicitly,
  or let the dev server choose a free one.
* **Run button and `run_mode`** — there is no Run button. Ask the agent to start
  the server; to avoid two servers fighting for one port, say so in `CLAUDE.md`.
* **Archive script** — runs only when you or the agent run it.

If the same steps apply across many repositories, store them once as a
[team skill](https://docs.nuphos.ai/agent/skills.md) so every agent on the team follows them.

### Let an agent convert them

Paste this into a Nuphos agent working in the repository:

> "This repo has Conductor config in `conductor.json` or
> `.conductor/settings.toml`. Move the setup, run, and archive scripts into
> `scripts/`, replace every `CONDUCTOR_*` variable with git or plain shell
> equivalents, and add a short section to `CLAUDE.md` (and `AGENTS.md` if it
> exists) telling an agent when to run each script. Leave the Conductor files in
> place and show me the diff before committing."

## 4. Bring over your agent sessions

Claude Code and Codex keep their own session history on your Mac, in
`~/.claude/projects` and `~/.codex/sessions`. Nuphos can pick those up:

**1. Start a new conversation**

Choose **New agent** and select the runtime you want to continue on.

**2. Open the session list**

In the composer, choose **+** → **Continue a Claude Code session** (or
**Continue a Codex session**) and pick the session.

**3. Keep going**

The session's turns become the new conversation's transcript, and the agent
treats them as its own prior context on your first message. Very long
sessions may leave out the oldest turns; the confirmation tells you how many.

The imported conversation is a normal Nuphos conversation, so you can later move
it to a cloud computer or invite a teammate into it.

## 5. Day-to-day in Nuphos

| You want to | In Nuphos |
| - | - |
| Run several tasks at once | Start one agent per task and split the window with **⌘D** |
| Keep a task going after closing the laptop | Move the conversation to a cloud computer or your own server from its runtime menu, then confirm **Move** |
| Check on an agent away from your desk | Open the conversation in the [iOS app](https://apps.apple.com/app/nuphos/id6812533633) |
| Bring in a teammate | @mention them in the conversation and choose **Invite** |
| Review a pull request or CI run | Open it in the [GitHub connector](https://docs.nuphos.ai/connectors/github.md) |
| Run something on a schedule | Create a [trigger](https://docs.nuphos.ai/agent/triggers.md) |

## 6. Remove Conductor

When every workspace you care about is pushed or moved:

1. Run `git worktree list` in each repository and confirm the worktrees you
   still need are outside `~/conductor`, or that their branches are pushed.
2. Quit Conductor and delete the app.
3. Remove leftover worktrees with `git worktree remove <path>`, then run
   `git worktree prune` in each repository.
4. Delete `~/conductor` once it is empty.
5. Remove `conductor.json` or `.conductor/` from repositories where you no
   longer need them.

## What's different

* **No automatic worktrees.** Conductor creates a branch and worktree for every
  workspace. In Nuphos the agent creates one when you ask, using git.
* **No setup or run script hooks.** Scripts run when you or the agent run
  them, guided by `CLAUDE.md`, `AGENTS.md`, or a team skill.
* **No built-in port allocation.** Choose ports explicitly.
* **More places to run.** The same conversation can move between your Mac, your
  own server, and a cloud computer.
* **Explicit sharing.** Team skills and team memory can be reused across the
  team. Conversation access, computer access and personal credentials have
  separate controls; belonging to a team does not make all private work public.

## FAQ

> [accordion] Do I need to re-clone my repositories?
>
> No. A local runtime works in the folders already on your Mac, including
> Conductor's worktrees. Clone again only when you move work to another
> computer, such as a cloud computer.

> [accordion] Does Nuphos charge for model usage?
>
> No. Each runtime signs in with your own Claude, ChatGPT, or other provider
> account, and inference runs on that subscription. Nuphos workspace plans are
> separate; see [Plans & billing](https://docs.nuphos.ai/billing.md).

> [accordion] Can I keep using Conductor while I try Nuphos?
>
> Yes. Both work on ordinary git worktrees. Avoid having two agents edit the
> same worktree at the same time.

> [accordion] Will Nuphos read my .conductor/settings.toml?
>
> No. Nuphos has no per-repo config file. Convert the scripts as described in
> [Convert your scripts](#3-convert-your-scripts).

> [accordion] Which agents can I use?
>
> Claude Code, Codex, OpenCode, Grok Build, and Antigravity. See
> [Supported runtimes](https://docs.nuphos.ai/agent/runtime.md#supported-runtimes) for where each can
> run.

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

Questions? 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.