Reinstate
Install

Use cases

Reinstate Use Cases for Cross-Device Coding-Agent Work

Reinstate helps developers find and continue local coding-agent sessions, then optionally move supported Claude Code or Codex sessions to 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.6.0-rc.6
Release status
v0.6.0-rc.6 candidate · stable remains v0.5.1 · v0.6.0-rc.5 tagged Windows run (plus two same-artifact rechecks) ended FAIL (211/4/0/0 of 215), zero product defects, grok:E1-E3 live-backend-connectivity plus a grok version drift to 1.0.13 and an H7 digest-equality-unmeasurable gap the four PARTIAL rows · this candidate widens the verified Grok Build range to 1.0.13 and refines the H7 live-home check to per-file listing with attribution · native Windows tagged-artifact acceptance pending, macOS deferred

Current continuity 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 running a pre-1.0 release 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 an agent below T5: Gemini CLI, Kimi Code CLI (T2), Grok Build or Qwen Code (T4 handoff, no sync), or a T0/T1 discover-only agent. See theintegrations page for exact tiers.
  • 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.

Stable v0.2.0 includes one-machine search. Stable v0.3.0 adds dual-platform verified resume. Stable v0.4.0 adds portable cross-agent checkpoints after tagged-artifact acceptance PASS. Stable v0.5.1 adds universal agent coverage by support tier. The v0.6.0-rc.6 release candidate carries Reinstate Hop and the interactive CLI, not yet certified; native Windows x64 acceptance is pending and Apple Silicon macOS is deferred. Non-secret configuration remains later roadmap work.

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.