Skip to content
Copperbar

Docs

Bring your local Conductor work

Copperbar can register existing local Conductor repositories and worktrees in place. Branches, files and uncommitted changes stay where they are. Chat history, provider authentication and running sessions are not imported.

Before you begin

Save cloud work onto a machine you control. Confirm that the branches and uncommitted files you need are present locally. Back up important work independently.

The official Conductor announcement says cloud workspaces become read-only on 13 November 2026 and shut down on 20 November 2026. Local Conductor support continues into early 2027.

Import

  1. Start Copperbar and choose From Conductor.
  2. Scan your local Conductor directory.
  3. Review the discovered projects and workspaces. Select only those you want to attach.
  4. Choose Review selected. Inspect the exact checkout paths, ownership, skipped items and proposed settings writes. Setup and archive commands are stored as settings; import does not run them.
  5. Choose Apply reviewed import, then inspect the attached workspace before starting an agent.

Copperbar does not automatically execute repository setup scripts during import. Imported workspaces remain externally owned. Archiving or undoing an import removes Copperbar’s references, not the source worktree files.

See installation for current availability. Copperbar is not an export service for Conductor Cloud.

Import history and recovery

Open Import history to inspect saved receipts, including the records created by an import and settings that were written. Export receipt downloads private metadata such as local paths and mapped commands. It does not export source files, Git objects or chat history; review the receipt before sharing it.

If the response is lost, the saved retry uses the original request key. Check history before retrying. An interrupted receipt can be reconciled with Reconcile interrupted import; this inspects recorded metadata and settings without restarting the import or replaying commands. Discarding a saved retry only clears this browser's retry record—it does not cancel or undo server work.

Undo removes only untouched Copperbar records created by that receipt. It leaves existing project/workspace records, source files and settings writes in place. If imported records have acquired sessions, notes or workflow references, automatic undo is refused to protect that work. Legacy receipts without sufficient ownership evidence require individual workspace detachment.

The reviewed snapshot covers Git-visible state and proposed settings. Ignored files remain in place but are not included in that fingerprint. Changed or relocated paths require a new review. Import is not a sandbox for other applications changing these files concurrently.