Product roadmap
Reinstate Roadmap: From Encrypted Sync to Work Continuity
Reinstate currently implements the Phase 0 foundation and Phase 1 encrypted same-vendor session-sync engine for Claude Code and Codex. Physical RC8 acceptance is still open. Local session search, verified resume, portable cross-agent handoffs, universal non-secret configuration, a thin console, and team continuity are later phases—not current capabilities.
- Last verified
- Current release
- v0.1.0-rc.8
- Release status
- pre-1.0 release candidate
- 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
v0.1.0-rc.8 supports encrypted same-vendor Claude Code and Codex session synchronization through user-owned S3-compatible storage. Native Windows, macOS amd64, WSL2, and full physical two-device acceptance still contain open release gates.
Phase map
| Phase | Outcome | Current state | Gate |
|---|---|---|---|
| 0 | Trustworthy contracts, diagnostics, installers, fixtures, CI, and documentation | In progress | Clean native-device and WSL2 acceptance |
| 1 | Encrypted same-vendor Claude Code and Codex session sync | Release candidate | Install, push, pull, restore, and native resume across the required matrix |
| 2 | Local universal session index, search, inspect, and native resume | Planned | Useful local-only continuation without remote configuration |
| 3 | Verified resume against repository, runtime, agent, MCP, and skill state | Planned | Report environment truth before launch and refuse silent bad continuation |
| 4 | Explicit portable checkpoints for cross-agent handoff | Planned | Lossy behavior and destination capability differences remain visible |
| 5 | Universal non-secret configuration and automatic cross-device reconciliation | Planned | Render native harness configuration without raw credential or config-tree mirroring |
| 6 | Optional thin console for selecting and preparing work | Exploring | Agents continue to own execution; Reinstate remains the continuity client |
| 7 | Team checkpoints, onboarding, provenance, and policy | Exploring | Individual continuity must first be proven safe and useful |
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 later portable handoff will carry an explicit checkpoint—goal, decisions, rejected approaches, files, tests, and next action—to a different agent. Reinstate will not market that lossy checkpoint as invisible transcript translation.
Universal configuration without unsafe mirroring
The planned configuration layer 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.