Reinstate
Install

Use cases

Reinstate Use Cases for Cross-Device Coding-Agent Work

Reinstate’s current release candidate is built for developers who need the same Claude Code or Codex session on another configured computer—especially a work and personal machine, or a Windows desktop and Mac laptop—with local encryption and user-owned storage between them.

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

Current Phase 1 use cases

Work and personal computers

Push an encrypted supported session from one configured device and pull it on another without requiring the source device to remain online.

Plan the two-device workflow →

macOS and Windows

Give one project a canonical ID, then map that identity to different native paths on a Mac and Windows PC.

Understand path remapping →

Desktop and laptop

Continue one selected same-vendor session on a portable or fixed computer without keeping the source machine online.

Plan desktop-to-laptop continuity →

Encrypted session backup

Create client-encrypted snapshots in storage you control while preserving the difference between Reinstate recovery and an independent backup strategy.

Review the backup boundary →

When Reinstate is a fit today

  • You use a tested Claude Code or Codex CLI version.
  • You want same-vendor continuity on another configured device.
  • Your repository lives at different absolute paths on the two machines.
  • You can use an S3-compatible bucket and retain the encryption passphrase safely.
  • You are comfortable evaluating a pre-1.0 release candidate and keeping backups.

When it is not yet a fit

  • You need Claude Code sessions converted into native Codex rollouts, or the reverse.
  • You use another agent such as Gemini CLI, OpenCode, Cursor, or Grok Build.
  • You need MCP servers, skills, plugins, agent credentials, or settings synchronized.
  • You need stable-v1 compatibility guarantees or a formally audited security product.
  • Your employer prohibits storing work artifacts in a personally controlled bucket.

Later roadmap phases broaden task continuity to one-machine search, verified resume, portable cross-agent checkpoints, and non-secret configuration. Those capabilities are not included in RC8.

The common continuity workflow

  1. Install the same pinned Reinstate version on each trusted device.
  2. Configure one profile, one bucket, and canonical IDs for the projects you will move.
  3. Push supported sessions from the device where the work currently exists.
  4. On the destination, inspect status and run a pull dry-run before restoring.
  5. Resume using the same native agent vendor after the project path is mapped locally.