Reinstate
Install

Integration · Claude Code

Sync Claude Code Sessions Across Devices | Reinstate

Reinstate syncs supported Claude Code sessions from one device to another, remaps configured project paths, and restores them to Claude Code’s native project layout. It supports Claude Code-to-Claude Code continuity only; it does not convert Claude transcripts into another agent’s format.

Last verified
Current release
v0.1.0-rc.8
Release status
pre-1.0 release candidate

Claude Code support at a glance

Session direction
Claude Code → Claude Code
Tested stable range
2.1.219–2.1.220
Primary platforms
macOS and native Windows
Remote storage
Your S3-compatible or Cloudflare R2 bucket

The tested range above is the current source compatibility evidence for macOS arm64 plus deterministic synthetic fixtures. Native Windows, macOS amd64, WSL2, and physical two-device acceptance remain release gates for stable v0.1. Versions outside the stated range are treated as UNTESTED and writes are blocked.

How Claude Code session sync works

Claude Code groups local sessions under a directory key derived from the device's absolute project path. Copying that directory unchanged from Windows to macOS is insufficient because the same repository normally lives at a different absolute path.

  1. During setup, map a stable project ID to the local project root on each device.
  2. On push, Reinstate associates discovered Claude sessions with that canonical project ID and encrypts the portable artifact locally.
  3. On pull, Reinstate resolves the destination device's project root and recomputes Claude Code's exact directory key for that path.
  4. RC8 verifies the restored session at the planned destination. A matching session ID elsewhere in Claude's project tree is not accepted as success.

Why project mapping is first-class

A repository might live at C:\src\app on Windows and/Users/you/src/app on macOS. Reinstate uses the shared project ID—not either machine's path—as portable identity.

What Reinstate does and does not sync

The adapter selects resumable Claude Code session artifacts. Reinstate excludes authentication files, OAuth or keychain material, tokens, caches, logs, and regenerable dependencies. Encrypted remote artifacts are stored in your bucket; the passphrase is not stored.

A transcript can still contain a secret that a person or tool printed into the conversation. Encryption reduces cloud-storage exposure, but you remain responsible for keeping production secrets out of agent chats. Read the complete security overview.

Current limitations

  • Claude Code sessions can be resumed only by Claude Code in Phase 1.
  • Unmapped projects are excluded when canonical project mappings are configured.
  • Untested or unsupported Claude Code layouts fail closed for push and pull.
  • Credentials, MCP servers, skills, plugins, hooks, and agent settings are not synced.
  • WSL1 is unsupported; native Windows and WSL2 are separate Reinstate devices.
  • Reinstate does not protect data on an already-compromised local machine.

Start with Claude Code

Install the current release candidate, run rein init, and give the same project a stable ID on both devices. Use rein push on the source and a dry-run beforerein pull on the destination. The step-by-step guide includes the exact commands and passphrase safety rules.