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.1. Install Nuphos and add a local runtime
1
Install the desktop app
Download Nuphos from 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.
3
Start an agent
Choose New agent in the sidebar and pick the local runtime in the
composer.
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:
“Work inThe 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. For a new task, ask the agent to create the worktree it needs, for example “create a worktree for a new branch~/conductor/workspaces/web/warsaw. It is on branchfix-login-redirect. Read the diff againstmainand continue the task.”
add-billing-export off origin/main and
work there”. Nuphos does not manage worktrees itself, so the agent uses
git worktree like you would.
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:
conductor.json
scripts/setup.sh
CLAUDE.md and Codex reads
AGENTS.md from the repository on its own:
CLAUDE.md
CONDUCTOR_ROOT_PATH— use the first entry ofgit worktree list, as above, or an absolute path.CONDUCTOR_WORKSPACE_PATH— the current directory, orgit 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 inCLAUDE.md. - Archive script — runs only when you or the agent run it.
Let an agent convert them
Paste this into a Nuphos agent working in the repository:“This repo has Conductor config inconductor.jsonor.conductor/settings.toml. Move the setup, run, and archive scripts intoscripts/, replace everyCONDUCTOR_*variable with git or plain shell equivalents, and add a short section toCLAUDE.md(andAGENTS.mdif 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.
5. Day-to-day in Nuphos
6. Remove Conductor
When every workspace you care about is pushed or moved:- Run
git worktree listin each repository and confirm the worktrees you still need are outside~/conductor, or that their branches are pushed. - Quit Conductor and delete the app.
- Remove leftover worktrees with
git worktree remove <path>, then rungit worktree prunein each repository. - Delete
~/conductoronce it is empty. - Remove
conductor.jsonor.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
Do I need to re-clone my repositories?
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.
Does Nuphos charge for model usage?
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.
Can I keep using Conductor while I try Nuphos?
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.
Will Nuphos read my .conductor/settings.toml?
Will Nuphos read my .conductor/settings.toml?
No. Nuphos has no per-repo config file. Convert the scripts as described in
Convert your scripts.
Which agents can I use?
Which agents can I use?
Claude Code, Codex, OpenCode, Grok Build, and Antigravity. See
Supported runtimes for where each can
run.
Is Nuphos open source? Can I self-host it?
Is Nuphos open source? Can I self-host it?
Yes. The source is at github.com/nuphos/nuphos,
and you can run your own backend. See Self-host.