Documentation

Reinstate's current release-candidate CLI syncs same-vendor Claude Code and Codex sessions between devices through client-side-encrypted S3-compatible storage. Universal configuration, cross-agent handoffs, and local session search remain roadmap work.

Prefer the short CLI alias rein. Full name reinstate is the same binary.

Guides

• Install and sync Reinstate across devices — Install Reinstate, configure encrypted S3-compatible storage, and restore a Claude Code or Codex session safely on another development machine.
• How Reinstate syncs coding-agent sessions — Understand Reinstate's adapters, structural path remapping, age encryption, immutable snapshots, conflict handling, and S3-compatible storage architecture.
• Claude Code and Codex session adapters — Learn how Reinstate adapters discover, normalize, and restore Claude Code and Codex sessions without translating native transcripts across vendors.
• Reinstate security and encryption model — See how Reinstate encrypts session data before upload, excludes credential files, stores storage keys, handles conflicts, and defines its threat boundaries.
• Universal agent configuration roadmap — Explore the planned non-secret desired-state model for rendering MCP servers, skills, hooks, plugins, marketplaces, and safe settings across coding agents.
• Reinstate compared with vendor and file sync — Compare Reinstate with native agent sync, session browsers, full agent development environments, single-agent utilities, and do-it-yourself file syncing.
• Reinstate frequently asked questions — Get direct answers about Reinstate's current session-sync scope, supported agents, encryption, storage, offline behavior, cross-agent handoffs, and roadmap.
• Troubleshoot Reinstate session sync — Fix Reinstate installation, compatibility, session selection, mapping, manifest, passphrase, conflict, credential, performance, and active-agent errors safely.
• Install the Reinstate CLI — Install the pinned Reinstate release candidate on macOS, native Windows, or WSL2, verify its checksum and version, and diagnose PATH failures.
• Configure Reinstate profiles and project paths — Configure a Reinstate profile, S3-compatible storage coordinates, OS-keyring credentials, and portable project mappings across development devices.
• Configure storage for encrypted Reinstate sessions — Understand Reinstate's S3-compatible storage fields, object layout, required permissions, encrypted payloads, profile isolation, and retention limits.
• Push one coding-agent session — Select, dry-run, encrypt, and push one supported Claude Code or Codex session to user-owned S3-compatible storage with Reinstate.
• Restore and resume one coding-agent session — Dry-run, safely restore, verify, and natively resume one encrypted Claude Code or Codex session on another configured device.
• Reinstate CLI command reference — Use every current Reinstate RC8 command with its purpose, parameters, expected evidence, platform notes, failure modes, and safe recovery path.
• Reinstate limitations and release-candidate boundaries — Review Reinstate RC8 limitations for agents, operating systems, native resume, storage, snapshots, path remapping, security, and release certification.