About Reinstate

What Is Reinstate? Coding-Agent Work Continuity

Reinstate is an open-source continuity layer for coding-agent work. Stable v0.2.0 moves encrypted Claude Code and Codex sessions between configured devices and adds configless local search plus same-vendor native resume/fork. Stable v0.3.0 adds verified resume. Stable v0.4.0 adds explicit structured cross-agent handoff after dual-platform tagged-artifact acceptance PASS. Stable v0.5.1 adds universal agent coverage by support tier after dual-platform tagged-artifact acceptance PASS. The v0.6.0-rc.6 release candidate carries Reinstate Hop (cloud continuity) and the interactive CLI; it is not yet certified, with tagged-artifact acceptance pending on native Windows x64 and Apple Silicon macOS deferred.

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

The problem Reinstate solves

Git moves source code, but it does not move the local history of a long coding-agent task: the rejected approaches, decisions, prompts, file context, and native session identifier. That history becomes fragmented across agents, projects, worktrees, operating systems, and devices.

Reinstate owns continuity before and after execution. Coding agents continue to own the actual execution loop. The goal is to let a developer find and continue a task in the right native environment without re-explaining it from scratch.

What is available today

Phase 1 implements the trust-sensitive sync engine and CLI surface for supported Claude Code and Codex CLI sessions:

  • Same-vendor session discovery, push, pull, status, diff, and conflict handling.
  • Local age encryption before upload to user-owned S3-compatible storage.
  • Canonical project identity and macOS ↔ Windows structural path remapping.
  • Credential exclusions, OS-keyring storage, restore backups, and atomic writes.
  • Checksum-verifying installers and compatibility checks that fail closed.
  • Configless local indexing, literal search, bounded inspect, and a TTY switcher.
  • Native same-vendor Claude Code/Codex resume and fork; read-only discovery across a wider agent catalog by support tier.
  • Phase 3 verified-resume reports and gates for repository, agent, capability, and runtime state.
  • Phase 4 structured handoff into a new Claude Code or Codex session.
  • Phase 5 universal agent coverage: one catalog, one support-tier ladder (T0–T5), honest T0.

Stable evidence stays platform-specific.

Stable v0.5.1 is physically verified on Apple Silicon macOS and native Windows x64 (dual-platform tagged-artifact acceptance PASS). Intel macOS and Linux/WSL2 packages are preview and unverified rather than inferred support. The v0.6.0-rc.6 release candidate — Reinstate Hop and the interactive CLI — is not yet certified; its acceptance is native Windows x64 only, with Apple Silicon macOS deferred until that hardware returns.

Latest public source tag
v0.6.0-rc.6(release candidate; cloud continuity and the interactive CLI, not yet a stable claim)
Latest stable release
v0.5.1
Initial public prerelease
Supported operating systems
Apple Silicon macOS and native Windows x64 verified; Intel macOS and Linux/WSL2 preview

Where the product goes next

PhaseDirectionStatus
1Encrypted same-vendor Claude Code and Codex session syncStable since v0.1.0
2Local universal session index, search, inspect, resume, and last-session commandsStable v0.2.0
3Verified resume against repo, branch, runtime, MCP, and skill statePhase 3 stable; dual-platform verified resume
4Explicit portable cross-agent checkpoints and capability diffsStable since v0.4.0
5Universal agent coverage: one catalog, one support-tier ladder, honest T0Stable since v0.5.0/v0.5.1
6CCloud continuity: Reinstate Hop (sign-in, locker, device pairing, daemon)v0.6.0-rc.6 release candidate; not yet certified, native Windows x64 acceptance pending, Apple Silicon macOS deferred
6A/6BUniversal non-secret configuration and automatic cross-device reconciliationPlanned for a later release
7Project continuity: durable rules and decisions rendered to every agent, plus learned memory with provenancePlanned for v0.8.0, after Phase 6A/6B
8+Optional thin console, then team continuityExploring

Later roadmap work is not present-day functionality. In particular, Reinstate does not provide cross-agent transcript translation, environment repair, configuration sync, or team handoffs.

What Reinstate is not

  • Not a code editor, terminal emulator, or full agentic development environment.
  • Not a multi-agent scheduler, model router, or worktree orchestrator.
  • Not a Reinstate-owned plugin runtime or marketplace.
  • Not raw mirroring of entire vendor configuration or credential trees.
  • Not silent Claude Code ↔ Codex transcript conversion.

Reinstate should integrate with the places developers already code. Its product boundary is whether work survives, can be found, and can continue safely—not where that work executes.

Who Reinstate is for

The primary audience is developers using terminal coding agents across multiple sessions, projects, or environments. A work desktop and personal laptop is the flagship multi-device case, especially across Windows and macOS, but physical device count is not the entire product identity.

The long-term north-star metric is previously started coding tasks successfully resumed per active user—not storage volume or device count.

Project and maintainer

Reinstate was created and is maintained byHarjot Singh Rana. The project is available onGitHub under the Apache License 2.0 and welcomes review, issues, and contributions.

Reinstate is independent of Anthropic, OpenAI, Google, xAI, and other agent vendors. Vendor names describe compatibility targets, not sponsorship or endorsement.