Claude Transplant banner
vitaliyhayda vitaliyhayda

Claude Transplant

Development community

Description

Move Claude Code history between accounts. Either via menubar or CLI. macOS only.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

claude-transplant

Move Claude Code history between accounts. Menubar or CLI.

Claude Transplant panel with source accounts converging on one destination

What it does

Claude Desktop lists each Claude Code session under the account and organization that created it. Switch accounts and the history stays behind. claude-transplant moves every eligible local Desktop record immediately, regardless of which account is signed in. The transcript and sidecars stay where they are, the session keeps its id, nothing is copied. Remote Control runs for the active source. An inactive source creates no pending check when every readable unarchived local conversation moved, while unreadable or unarchived records left behind remain pending. No model runs and no artifact is recreated. `undo` restores completed work and cancels unfinished cloud sources as one logical move. macOS only.

Install

Node 22 or newer. The menubar also needs the Xcode command line tools once: `xcode-select --install`.

npx claude-transplant menubar
npx claude-transplant

To run from this repository instead of npm: `npx github:vitaliyhayda/claude-transplant`, with `#v3.0.1` or a commit hash to pin.

The menubar shows two columns of email over plan, with FROM on the left and TO on the right. TO starts on the most recently used account other than the signed-in one, while every other account starts selected as a source. Uncheck only the accounts to leave behind. Curves converge on TO, chevrons show direction, destination changes swap lane identity, and source changes fade only that lane. Long inventories scroll together. The active account is tagged, pending sources are tagged, and Finish pending becomes available when one is active. Keep local abandons pending cloud work without reversing successful local movement. It s