Product roadmap

Reinstate Roadmap: From Encrypted Sync to Work Continuity

Stable v0.2.0 implements encrypted same-vendor sync and local continuity. 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. Stable v0.6.0 adds Phase 6C cloud continuity (Reinstate Hop) and the interactive CLI, certified by native Windows x64 tagged-artifact acceptance PASS under a single-platform waiver (ADR 0005); Apple Silicon macOS acceptance is deferred to issue #403. Phase 6A/6B universal configuration remains planned. Phase 7 is project continuity, planned and targeted at v0.8.0. Phase 8 is Console. Phase 9 is team continuity.

Last verified
Current release
v0.6.0
Release status
v0.6.0 stable · native Windows x64 tagged-artifact acceptance PASS (215/215 required rows, docs/testing/results/2026-09-09-windows-v060rc8.md) under the single-platform waiver (ADR 0005) · Apple Silicon macOS acceptance deferred to #403 · supersedes v0.5.1

How to read this roadmap

A checked implementation item is not automatically a stable product claim. Each phase has an evidence gate, and the public compatibility page remains the source for what a released binary may mutate safely. Priorities can change with real activation data and coding-agent format changes.

Current release boundary

Stable v0.6.0 supports encrypted same-vendor Claude Code, Codex, and OpenCode session synchronization, configless local continuity, verified resume, structured handoff, universal agent coverage by support tier, Reinstate Hop (cloud continuity), and the interactive CLI experience. Certified by native Windows x64 tagged-artifact acceptance PASS under the single-platform waiver in ADR 0005; Apple Silicon macOS acceptance is deferred to issue #403 until that hardware returns. Earlier stable releases (v0.5.1 and before) passed dual-platform tagged-artifact acceptance on both Apple Silicon macOS and native Windows x64; Intel macOS and Linux/WSL2 remain preview and unverified. See the changelog for the exact pinned tag.

Phase map

PhaseOutcomeCurrent stateGate
0Trustworthy contracts, diagnostics, installers, fixtures, CI, and documentationCompleteReleased foundation and evidence contracts
1Encrypted same-vendor Claude Code and Codex session syncStableVerified on Apple Silicon macOS and native Windows x64
2Local universal session index, search, inspect, and native resumeStableComplete physical matrix on the two verified stable platforms
3Verified resume against repository, runtime, agent, MCP, and skill stateStableDual-platform tagged-artifact acceptance PASS; stable published
4Explicit portable checkpoints for cross-agent handoffStableDual-platform tagged-artifact acceptance PASS on Apple Silicon macOS and native Windows x64. Lossy behavior and destination capability differences remain visible
5Universal agent coverage: one catalog, one support-tier ladder, honest T0In progressv0.5.0 artifacts discover, search, and inspect additional agents only at the committed tier. No new T4 destinations or T5 sync agents
6Universal non-secret configuration and automatic cross-device reconciliationSplit: cloud continuity (6C, the Hop client) shipped stable in v0.6.0, certified on native Windows x64 (macOS deferred, #403); universal configuration (6A/6B) remains planned for v0.7.0Render native harness configuration without raw credential or config-tree mirroring
7One project understanding: durable rules and decisions rendered to every agent, plus learned memory with provenancePlannedState a rule once and have every gated harness honor it; capture a memory in one agent's session and retrieve it, with provenance, from another; flag a memory a later decision contradicts
8Optional thin console for selecting and preparing workExploringAgents continue to own execution; Reinstate remains the continuity client
9Team checkpoints, onboarding, provenance, and policyExploringIndividual continuity must first be proven safe and useful

Phase 5 — Universal agent coverage

Phase 5 replaces five agents described in prose with one catalog and a six-rung tier ladder. Public surfaces state the rung. Encrypted sync stays Claude Code and Codex CLI. Native resume stays same-vendor.

ItemStatus
Catalog core and the five shipped agents at unchanged tiersIn progress
Wave A/B/C descriptors at T0 with a recorded reasonIn progress
Gemini CLI promotion from T2 to T3Stays T2
New T4 destinations or T5 sync agentsOut of scope
Phase 5 dual-platform tagged-artifact acceptancePlanned

Native resume and portable handoff stay distinct

Native resume preserves a vendor's own session format: Claude Code resumes Claude Code, and Codex resumes Codex. A structured handoff is a different operation, added in stablev0.4.0: it carries an explicit checkpoint—goal, decisions, rejected approaches, files, tests, and next action—so a new session in another agent can continue the same task. It is not a resume of the original session, and Reinstate will not market that lossy checkpoint as invisible transcript translation.

Universal configuration without unsafe mirroring

Phase 6, not Phase 5, is the configuration and cloud-continuity layer, and it now splits in two. Cloud continuity (6C), the Hop client for encrypted multi-device sync, is in release preparation ahead of the rest. Universal configuration (6A/6B) remains planned: it will describe portable intent for MCP servers, skills, instructions, hooks, plugins, marketplaces, and safe settings. Adapters will preview and render each supported harness's native format. Raw API keys, OAuth tokens, cookies, vendor credential stores, and unrelated native settings remain excluded.

Near-term non-goals

  • A custom editor, terminal emulator, or full agentic development environment.
  • A multi-agent scheduler, model router, or worktree orchestration platform.
  • A proprietary agent plugin runtime or marketplace.
  • Replacing Git as source truth.
  • Perfect silent Claude Code ↔ Codex transcript translation.
  • Shipping vendor credentials or mirroring complete configuration trees.

How priorities move

The north-star measure is previously started coding tasks successfully resumed per active user. Device count and storage volume are not substitutes. The maintainer will weigh real continuation failures, compatibility churn, security risk, and repeated user requests before promoting a planned phase.

The repository'sversion-controlled roadmap is authoritative for item-level status. Open a sourced issue or discussion to propose a change.