Migrate from Conductor
Copperbar is a Mac app for working with coding agents. There is no Conductor account to sign into, and chat history is not imported. You keep working in the git checkouts already on disk.
Three-step import
- 01
Pull Cloud work onto a machine you control
While Conductor Cloud is still writable, sync the branches and uncommitted files you need into local folders (commonly ~/conductor/repos and ~/conductor/workspaces).
- 02
Check Mac app availability
Public downloads are being prepared. Check availability before planning your move. If you already have the Mac beta, open Copperbar to begin.
- 03
Open in place from Conductor
Choose From Conductor and scan your local folders. Select the projects and workspaces you want, choose Review selected, inspect the paths and optional settings changes, then choose Apply reviewed import. Your existing branches and files stay in place.
What is imported
- The local Git repositories you select
- Linked worktrees attached as Copperbar workspaces
- Optional mapping of setup/archive scripts into
.copperbar/settings.toml(skipped if keys exist) CONDUCTOR_PORT*env compatibility in scripts
What is not imported
- Chat / session transcripts from Conductor SQLite
- Conductor Cloud microVMs or hosted runtime
- Any Copperbar-hosted replacement for Cloud compute
Keep your existing worktree files
Import never deletes, moves, archives, or runs setup under ~/conductor/. Do not archive workspaces in Conductor as a “cleanup” step — archiving there can delete on-disk folders. Keep the folders; point Copperbar at them.