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. The v0.6.0-rc.6 release candidate carries Phase 6C cloud continuity (Reinstate Hop) and the interactive CLI; it is not yet certified, with tagged-artifact acceptance pending on native Windows x64 and Apple Silicon macOS deferred; the public installers already pin this candidate while that acceptance run is pending. 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-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
- Owner
- Harjot Singh Rana
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.5.1 supports encrypted same-vendor Claude Code and Codex session synchronization, configless local continuity, verified resume, structured handoff, and universal agent coverage by support tier, after dual-platform tagged-artifact acceptance PASS. Apple Silicon macOS and native Windows x64 remain the verified stable platforms; Intel macOS and Linux/WSL2 remain preview and unverified. The v0.6.0-rc.6 release candidate carries Reinstate Hop and the interactive CLI experience but is not yet certified; its tagged-artifact acceptance is pending on native Windows x64 only, with Apple Silicon macOS deferred until that hardware returns. The public installers already pin this candidate while that acceptance run is pending; see the changelog for the exact pinned tag.
Phase map
| Phase | Outcome | Current state | Gate |
|---|---|---|---|
| 0 | Trustworthy contracts, diagnostics, installers, fixtures, CI, and documentation | Complete | Released foundation and evidence contracts |
| 1 | Encrypted same-vendor Claude Code and Codex session sync | Stable | Verified on Apple Silicon macOS and native Windows x64 |
| 2 | Local universal session index, search, inspect, and native resume | Stable | Complete physical matrix on the two verified stable platforms |
| 3 | Verified resume against repository, runtime, agent, MCP, and skill state | Stable | Dual-platform tagged-artifact acceptance PASS; stable published |
| 4 | Explicit portable checkpoints for cross-agent handoff | Stable | Dual-platform tagged-artifact acceptance PASS on Apple Silicon macOS and native Windows x64. Lossy behavior and destination capability differences remain visible |
| 5 | Universal agent coverage: one catalog, one support-tier ladder, honest T0 | In progress | v0.5.0 artifacts discover, search, and inspect additional agents only at the committed tier. No new T4 destinations or T5 sync agents |
| 6 | Universal non-secret configuration and automatic cross-device reconciliation | Split: cloud continuity (6C, the Hop client) is in release preparation as a candidate; universal configuration (6A/6B) remains planned for a later release | Render native harness configuration without raw credential or config-tree mirroring |
| 7 | One project understanding: durable rules and decisions rendered to every agent, plus learned memory with provenance | Planned | State 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 |
| 8 | Optional thin console for selecting and preparing work | Exploring | Agents continue to own execution; Reinstate remains the continuity client |
| 9 | Team checkpoints, onboarding, provenance, and policy | Exploring | Individual 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.
| Item | Status |
|---|---|
| Catalog core and the five shipped agents at unchanged tiers | In progress |
| Wave A/B/C descriptors at T0 with a recorded reason | In progress |
| Gemini CLI promotion from T2 to T3 | Stays T2 |
| New T4 destinations or T5 sync agents | Out of scope |
| Phase 5 dual-platform tagged-artifact acceptance | Planned |
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.