How do I move a Claude Code Montage workflow to another working copy?
Opening another checkout is a configuration transition, not a reason to assume that server registration or account access followed the files. Move only the documented remote connection intent and establish a fresh baseline in the destination working copy. The move should preserve registration intent without transporting account state. Compare both working copies explicitly so a destination success is not confused with source revocation or automatic consent inheritance.
Help me move a Claude Code Montage workflow to another working copy. Identify which server entry the original Claude Code session uses and whether its reach is tied to the project or user. After a bounded signals_status check in the new context, update your own working instructions to name the active entry. No writes.Inventory the source checkout
Identify which server entry the original Claude Code session uses and whether its reach is tied to the project or user. Do not export authorization storage with repository files. The migration inventory should distinguish repository-local instructions from configuration that belongs to the user across multiple checkouts.
Compare destination registration
Inspect the new working copy’s existing Montage entries before copying instructions. A different local server with a familiar name must not be silently replaced by a migration recipe. Compare a similarly named server’s destination before deciding which entry is intended; naming alone cannot establish ownership or correctness.
Retain the remote transport
Use the documented HTTP registration path only if a destination entry is needed. Keep configuration migration distinct from installing a local server or changing the project’s application dependencies. The known HTTP add command registers a server address; it should not be represented as an installer or login command.
Authenticate in the destination context
Use /mcp if the destination session requests authorization. Treat another checkout’s successful consent as evidence about that session only, not a transferable credential bundle. If the destination cannot open the documented consent flow, preserve that client capability blocker rather than exporting source-machine tokens.
Retire ambiguous instructions
After a bounded signals_status check in the new context, update your own working instructions to name the active entry. Preserve unrelated checkout configuration and do not claim the old environment was disconnected. Keep a destination-specific status note so later debugging can identify which checkout and account context were actually verified.
Keep the boundaries clear.
- The known HTTP add command registers a server address; it should not be represented as an installer or login command.
- Keep a destination-specific status note so later debugging can identify which checkout and account context were actually verified.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.