Anthropic’s Claude Desktop has a nasty habit of hiding your local coding history when you switch accounts, but a new community tool called claude-migrate finally fixes it. Released on October 13, 2026, this macOS-only utility doesn’t magically restore deleted data; it simply points the new account’s sidebar to the session records already sitting on your disk. For developers juggling personal and team environments, this eliminates the frustrating 'empty sidebar' syndrome that occurs when moving from a personal to a Team account.

How It Works

The tool operates on a critical architectural detail: Claude Desktop stores transcripts and sidebar metadata separately. The transcripts live in ~/.claude/projects/ and are account-agnostic, meaning they persist regardless of which account is signed in. However, the sidebar records—the JSON files that actually tell the UI to display a session—are locked to specific account and organization folders. claude-migrate copies these sidebar records from the old account’s store to the new one, preserving the session IDs so that any pinned sessions remain pinned. It’s a surgical move that respects the existing file structure without touching the actual conversation data.

Safety and Design

What stands out in the technical documentation is the tool’s defensive posture. It defaults to a dry run, requiring an explicit 'apply' command to write any changes. The safety model is rigorous: every write is logged to a manifest with a SHA-256 hash, allowing for a precise 'undo' function that only deletes files created by the migration if they haven’t been modified since. It also refuses to run if Claude Desktop is active, preventing race conditions, and fails closed on any unrecognized folder layouts. This isn’t a hacky script; it’s a carefully engineered bridge over Anthropic’s undocumented internals.

Key Takeaways

  • The tool is strictly for macOS and handles only local Desktop Code sessions; cloud sessions and Cowork data are out of scope.
  • Migration is additive only; it never overwrites existing files in the target account, reducing the risk of data loss.
  • Pins are preserved because the tool keeps the original session IDs, leveraging Desktop’s global pin list stored in claude_desktop_config.json.
  • Scheduled tasks are not migrated automatically and must be recreated in the new account.

The Bottom Line

This is a classic case of the community out-engineering the vendor’s UX. While Anthropic’s reliance on undocumented local file structures is brittle, claude-migrate offers a robust, safe, and transparent solution for a problem that has plagued Claude Code users for months.

Final Analysis

The existence of tools like claude-migrate highlights a growing trend: as LLM agents become more integrated into local dev environments, the gap between cloud-based AI and local state management creates friction. Anthropic needs to standardize how session metadata is handled across account switches. Until then, this Go binary is the best insurance policy for your coding context.