Guides
Guides
Use these step-by-step guides to configure encrypted, same-vendor coding-agent session sync across two devices. Every command is checked against the current Reinstate release candidate and includes dry-run, path-mapping, security, and verification steps.
- Last verified
- Current release
- v0.1.0-rc.8
- Release status
- pre-1.0 release candidate
- Owner
- Harjot Singh Rana
Session sync guides
Start with the coding agent whose session you need to move. Phase 1 preserves each vendor's native format: Claude Code resumes Claude Code sessions, and Codex resumes Codex sessions.
General · 17 min
Move a Coding-Agent Session from Mac to Windows
Move one encrypted Claude Code or Codex session from macOS to native Windows with RC8 path remapping, dry-runs, backups, and native resume.
Read guide →Claude Code · 12 min
How to Sync Claude Code Sessions Across Devices
Set up encrypted Claude Code session sync between two computers with Reinstate, including project path mapping, dry runs, restore, and native resume.
Read guide →Codex CLI · 12 min
How to Sync Codex Sessions Across Devices
Set up encrypted Codex CLI session sync between two computers with Reinstate, including project mapping, dry runs, safe restore, and native resume.
Read guide →General · 14 min
Use Cloudflare R2 for Encrypted Coding-Agent Session Storage
Configure a private Cloudflare R2 bucket and bucket-scoped S3 credentials for Reinstate RC8, then verify encrypted Claude Code or Codex storage.
Read guide →General · 15 min
Use Amazon S3 for Encrypted Coding-Agent Session Storage
Configure a private Amazon S3 bucket and least-privilege credentials for Reinstate RC8, then verify encrypted Claude Code or Codex session storage.
Read guide →Start with one harmless session
Evaluate Reinstate with a non-sensitive session and an explicit session ID. Confirm the destination mapping in a dry run before a mutating pull, and keep the coding agent closed when replacing an existing local session.