Compatibility history
Claude Code and Codex Version Support History
Reinstate v0.6.0-rc.6 (stable v0.5.1) accepts Claude Code versions 2.1.219–2.1.263 and Codex CLI versions 0.133.0–0.149.0, each on evidence reviewed 2026-08-16; versions outside the ranges still fail closed.
- Published
- 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
Current tested stable ranges
| Agent | Inclusive range | Resume mode | Evidence reviewed |
|---|---|---|---|
| Claude Code | 2.1.219–2.1.263 | Claude Code to Claude Code (T5 encrypted sync; T3 same-vendor resume) | Immutable test source |
| OpenAI Codex CLI | 0.133.0–0.149.0 | Codex to Codex (T5 encrypted sync; T3 same-vendor resume) | Immutable test source |
| Gemini CLI | 0.55.1–0.55.1 | Handoff source only (T2); no native resume | Immutable test source |
| OpenCode | 1.18.21–1.18.29 | OpenCode to OpenCode (T5 encrypted sync; T3 same-vendor resume and fork); OpenCode as a structured handoff destination (T4) | Immutable test source |
| Grok Build | 1.0.5–1.0.13 | Same-vendor native resume via grok --resume <uuid> (T3); handoff destination via grok --session-id <uuid> (T4) | Immutable test source |
| Pi | 0.73.1–0.73.1 | Not usable (T1 discover only) | Immutable test source |
| Qwen Code | 0.21.12–0.23.0 | Qwen Code to Qwen Code (T3 same-vendor resume and fork); Qwen Code as a structured handoff destination (T4) | Immutable test source |
The matrix is rendered from the same committed compatibility data asthe public compatibility page. Ranges cover stable three-component versions only. A prerelease, malformed version, or version below or above the inclusive endpoints is not silently accepted.
What happens outside a tested range
A recognizable installed agent outside the tested range is UNTESTED.rein setup check exits with compatibility code 5, and the Phase 1 CLI blocks session export and restore. There is no public unsafe override in the current CLI.UNSUPPORTED and NOT_INSTALLED also prevent mutation.
This source-level gate is necessary but does not certify every operating system. Native Windows, macOS amd64, WSL2, and the complete Reinstate two-device matrix retain separate physical acceptance evidence on the current matrix.
Release-by-release compatibility tracker
| Reinstate release | Date | Agent-version range | Related compatibility change |
|---|---|---|---|
| v0.6.0-rc.6 | Widens the verified Grok Build range to 1.0.5-1.0.13 (was the single 1.0.5 build), on the maintainer's own console evidence, under ADR 0005 D3: the acceptance host's Grok Build self-updated past the in-tree 1.0.5 ceiling, and the pinned 1.0.5 binary no longer completes a prompt against xAI from any console, including the maintainer's own, while 1.0.13 answers instantly there. This widening's own evidence is read-only (grok --version/--help output shape, and the session file layout and JSON key names observed under a real Grok home); version-output parsing and every launch-plan-relevant --help flag (--resume, --fork-session, --continue, --session-id) are unchanged from 1.0.5. Completed-turn grok:E1-E3 evidence against 1.0.13 is executed by the maintainer at their own console in this candidate's tagged run. Claude Code (2.1.219-2.1.263), Codex CLI (0.133.0-0.149.0), OpenCode (1.18.21-1.18.29), and Qwen Code (0.21.12-0.23.0) ranges are unchanged. macOS evidence is pending. | Corrective candidate after v0.6.0-rc.5 tagged-artifact acceptance on native Windows x64, plus two same-artifact rechecks, ended device verdict FAIL (211/4/0/0 of 215 required rows, zero product defects). Refines the MatrixH:H7 live-home acceptance check from aggregate byte-for-byte digest equality of the live agent-home roots (shown unmeasurable on a live, multi-session host by both rc.5 rechecks) to a full per-file before/after listing of only the session-bearing subtrees with per-entry attribution to a process other than rein. Schedules issue #424 (the daemon Task-Scheduler task not pinning the agent-root environment it was installed under) for v0.6.1 rather than this candidate. No agent tier changes. See CHANGELOG.md. Tagged implementation. | |
| v0.6.0-rc.5 | Widens the verified OpenCode range to 1.18.21-1.18.29 (was 1.18.21-1.18.27 through v0.6.0-rc.4), on native Windows evidence only, under ADR 0005 D3: against the shared live OpenCode store, a real OpenCode 1.18.29 session was created in a throwaway project and identified by a token planted in its own first turn, then indexed, resumed, and forked through the launch plan Reinstate produces, and the resumed session returned that same token. Session row shape (session/message/part tables and columns), --session, --session --fork, --continue, the non-interactive run form, version-output parsing, and the structured-handoff capsule path are unchanged from 1.18.27. Claude Code (2.1.219-2.1.263) and Qwen Code (0.21.12-0.23.0) ranges are unchanged. macOS evidence is pending. | Corrective candidate after v0.6.0-rc.4 tagged-artifact acceptance on native Windows x64 ended device verdict FAIL (208/1/4/2 of 215 required rows; both of that candidate's own fixes, the Pi reader and the widened Qwen Code range, were confirmed). Fixes the agent probe redaction gap that let real project-name path segments reach a committed artifact unshaped (MatrixB:B4), the gap where an existing-but-empty overridden agent root was indistinguishable from an absent one (MatrixB:B7), and the interactive switcher's all-projects readiness defect that showed every visible row as unresumable regardless of true state. Widens the verified OpenCode range to 1.18.29. No agent tier changes. See CHANGELOG.md. Tagged implementation. | |
| v0.6.0-rc.4 | Widens the verified Qwen Code range to 0.21.12-0.23.0 (was 0.21.12-0.21.13 through v0.6.0-rc.3), on native Windows physical-resume evidence only, under ADR 0005 D3: a real Qwen Code 0.23.0 session was created, indexed, resumed, and forked through the launch plan Reinstate produces, and the resumed session returned a token that existed only in the original session's history. Session file location and naming, the first-user-message shape, --resume, --resume --fork-session, --session-id, and version-output parsing are unchanged from 0.21.13. Claude Code (2.1.219-2.1.263) and OpenCode (1.18.21-1.18.27) ranges are unchanged. macOS evidence for the widened part is pending. | Corrective candidate after v0.6.0-rc.3 tagged-artifact acceptance on native Windows x64 ended device verdict FAIL (201/3/1/10 of 215 required rows; all 22 CLI rows and all 16 Hop rows passed, and the Cursor CLI store-schema fix was confirmed on real data). Fixes exactly two things: the Pi reader now indexes message.content for prompt_preview and search text (a confirmed code defect, pi:C3), and the verified Qwen Code range widens to 0.23.0 (a version-compatibility block, not a defect). No agent tier changes. See CHANGELOG.md. Tagged implementation. | |
| v0.6.0-rc.3 | Unchanged from v0.6.0-rc.2: inclusive Claude Code range 2.1.219-2.1.263 and OpenCode range 1.18.21-1.18.27. The Codex CLI range stays 0.133.0-0.149.0. | Corrective candidate after v0.6.0-rc.2 tagged-artifact acceptance on native Windows x64 ended device verdict FAIL (203/5/2/5 of 215 required rows). Fixes exactly the Cursor CLI store reader: a post-commit schema-only inspection of real Cursor CLI 2026.08.11 store.db files found blobs/meta tables, not the messages/message/bubbles shape the prior reader guessed at, so message_count and search_text now read the real schema. No agent tier changes. See CHANGELOG.md. Tagged implementation. | |
| v0.6.0-rc.2 | Unchanged from v0.6.0-rc.1: inclusive Claude Code range 2.1.219-2.1.263 and OpenCode range 1.18.21-1.18.27. The Codex CLI range stays 0.133.0-0.149.0. | Corrective candidate after v0.6.0-rc.1 tagged-artifact acceptance on native Windows x64 found 7 required-row failures (201 of 216 rows passed). No agent tier changes; fixes Cursor CLI session-discovery isolation, Cline/Cursor message_count and Cursor size_bytes, push/pull --agent completion, OpenCode handoff determinism, and adds Windows-shaped partial-final-record fixtures for Claude Code, Codex, and Grok Build. See CHANGELOG.md. Tagged implementation. | |
| v0.6.0-rc.1 | Widens the inclusive Claude Code range to 2.1.219-2.1.263 (was 2.1.219-2.1.238 through v0.5.2-rc.1) and the OpenCode range to 1.18.21-1.18.27 (was the single 1.18.21 build). The Codex CLI range is unchanged at 0.133.0-0.149.0. Both new ceilings rest on native Windows physical resume evidence only, under ADR 0005: a session created with the installed version was indexed and resumed through the launch plan Reinstate produced, returning a token that existed only in that session's history. Apple Silicon macOS evidence for the widened part is pending. | Carries the Hop client: OpenCode reaches encrypted sync (T5) and Kimi Code CLI becomes a handoff source (T2). Both are merged into this candidate but not yet part of a stable release; the published compatibility matrix moves with the tag, not with the tree. Tagged implementation. | |
| v0.5.2-rc.1 | |||
| v0.5.1 | Unchanged from v0.5.0: inclusive Claude Code range 2.1.219-2.1.238 and Codex CLI range 0.133.0-0.149.0. | Patch release. Updates the pure-Go SQLite driver behind the session index and the OpenCode embedded store. No product code changed, and no agent tier moved. Tagged implementation. | |
| v0.5.0 | Inclusive Claude Code range 2.1.219-2.1.238 and Codex CLI range 0.133.0-0.149.0, each raised on dual-platform physical resume evidence during the Phase 5 candidates. | Stable Phase 5 release. Universal agent coverage across a catalog of 18 agents, with Claude Code and Codex remaining the only native resume and sync surfaces. Authorized by dual-platform tagged-artifact acceptance on v0.5.0-rc.6. Tagged implementation. | |
| v0.5.0-rc.6 | Unchanged from v0.5.0-rc.5: inclusive Claude Code range 2.1.219-2.1.238 and Codex CLI range 0.133.0-0.149.0. | Sixth Phase 5 candidate. Carries the single defect physical v0.5.0-rc.5 acceptance found: the agent probe emitted a raw 38-character Git object hash, because the shape normaliser recognised only exactly 32, 40 and 64 characters while OpenCode keeps a Git object store under each snapshot. A committed probe artifact must not carry a content hash of the operator own repository. Claude Code and Codex remain the only T3-T5 surfaces. This candidate does not authorize stable v0.5.0. Tagged implementation. | |
| v0.5.0-rc.5 | Raises both inclusive ranges on dual-platform physical evidence: Claude Code to 2.1.219-2.1.238 and Codex CLI to 0.133.0-0.149.0. On macOS and on Windows a session created with the new version was indexed by Reinstate, resumed through the launch plan Reinstate produced, and returned a token that existed only in the original session history. | Fifth Phase 5 candidate. Fixes an index that never re-read a source after Reinstate itself changed, so a reader fix reached nobody who already had an index. Also recovers Gemini project paths on case-insensitive filesystems, makes an agent root override authoritative when it names a missing path, and skips parsing an unchanged source. Claude Code and Codex remain the only T3-T5 surfaces. This candidate does not authorize stable v0.5.0. Tagged implementation. | |
| v0.5.0-rc.4 | Raises both inclusive ranges on dual-platform physical evidence: Claude Code to 2.1.219-2.1.238 and Codex CLI to 0.133.0-0.149.0. On macOS and on Windows a session created with the new version was indexed by Reinstate, resumed through the launch plan Reinstate produced, and returned a token that existed only in the original session history. | Fourth Phase 5 candidate. Makes the agent probe reproducible, normalizes raw content hashes out of probe output, refuses native actions on a T0 agent with the compatibility exit code, narrows an agent-filtered refresh to that agent, and completes agent keys per flag. Claude Code and Codex remain the only T3-T5 surfaces. This candidate does not authorize stable v0.5.0. Tagged implementation. | |
| v0.5.0-rc.3 | Unchanged from v0.5.0-rc.2: inclusive Claude Code range 2.1.219-2.1.229. The Codex CLI range is unchanged at 0.133.0-0.147.0. | Third Phase 5 candidate. Restores Kimi, Copilot, and OpenCode session discovery after those vendor CLIs changed their on-disk formats. Claude Code and Codex remain the only T3-T5 surfaces. This candidate does not authorize stable v0.5.0. Tagged implementation. | |
| v0.5.0-rc.2 | Unchanged from v0.5.0-rc.1: inclusive Claude Code range 2.1.219–2.1.229. The Codex CLI range is unchanged at 0.133.0–0.147.0. | Second Phase 5 candidate after v0.5.0-rc.1 dual-platform tagged-artifact acceptance FAILED. Structured-handoff projection pairs tool_result with its tool_call. Claude Code and Codex remain the only T3–T5 surfaces. This candidate does not authorize stable v0.5.0. Tagged implementation. | |
| v0.5.0-rc.1 | Unchanged from v0.4.0: inclusive Claude Code range 2.1.219–2.1.229. The Codex CLI range is unchanged at 0.133.0–0.147.0. | First Phase 5 candidate. Six T1 discover agents and three T2 handoff sources. Claude Code and Codex remain the only T3–T5 surfaces. Dual-platform tagged-artifact acceptance FAILED (macOS 88/150, Windows 93/150); this candidate does not authorize stable v0.5.0. Tagged implementation. | |
| v0.4.0 | Unchanged from v0.4.0-rc.11: inclusive Claude Code range 2.1.219–2.1.229. The Codex CLI range is unchanged at 0.133.0–0.147.0. | Phase 4 stable after dual-platform tagged-artifact acceptance PASS on v0.4.0-rc.11 (Apple Silicon macOS 44/44, native Windows x64 44/44). Structured handoff continues the same task in a new Claude Code or Codex session. Native resume remains same-vendor. Gemini CLI, OpenCode, and Grok Build remain handoff sources only. Tagged implementation. | |
| v0.4.0-rc.11 | Unchanged from v0.4.0-rc.10: inclusive Claude Code range 2.1.219–2.1.229. The Codex CLI range is unchanged at 0.133.0–0.147.0. | Eleventh Phase 4 candidate after v0.4.0-rc.10 physical dual-platform acceptance FAILED (macOS 41/44 A1/A3/A7, Windows 40/44 A1/A2/A3/A5). This candidate requires the five-bullet dest first-reply in bootstrap and Windows one-line argv, records lineage before dest Launch, recovers artifact dirs in handoff list, and Materializes dest-home workspace trust. Dual-platform tagged-artifact acceptance later PASS (macOS 44/44, Windows 44/44); promoted to stable v0.4.0. Tagged implementation. | |
| v0.4.0-rc.10 | Unchanged from v0.4.0-rc.9: inclusive Claude Code range 2.1.219–2.1.229. The Codex CLI range is unchanged at 0.133.0–0.147.0. | Tenth Phase 4 candidate after v0.4.0-rc.9 physical dual-platform acceptance FAILED (macOS 38/44, Windows 38/44). This candidate falls back to a one-line absolute projection.md pointer whenever dest briefing contains CR/LF so Windows CreateProcess cannot truncate argv. Physical dual-platform acceptance FAILED (macOS 41/44 A1/A3/A7, Windows 40/44 A1/A2/A3/A5; remaining product defects dest first-reply, lineage-after-launch, dest folder-trust); this candidate does not authorize stable v0.4.0. Tagged implementation. | |
| v0.4.0-rc.9 | Unchanged from v0.4.0-rc.8: inclusive Claude Code range 2.1.219–2.1.229. The Codex CLI range is unchanged at 0.133.0–0.147.0. | Ninth Phase 4 candidate after v0.4.0-rc.8 physical dual-platform acceptance FAILED (macOS 38/44, Windows 38/44). This candidate maps a recognized off-PATH layout to inspect JSON status=supported without claiming a verified version range, and still fail-closes destination launch when the executable is missing. Physical dual-platform acceptance FAILED (macOS 38/44, Windows 38/44; dest-ack A4 PASS, A1/A2/A3/A5/A6/A7 FAIL; remaining product defect Windows dest argv CR/LF truncation); this candidate does not authorize stable v0.4.0. Tagged implementation. | |
| v0.4.0-rc.8 | Unchanged from v0.4.0-rc.7: inclusive Claude Code range 2.1.219–2.1.229. The Codex CLI range is unchanged at 0.133.0–0.147.0. | Eighth Phase 4 candidate after v0.4.0-rc.7 physical dual-platform acceptance FAILED (macOS 38/44, Windows 34/44). This candidate scans recognized Claude layout on off-PATH Inspect instead of returning before the layout scan (R1) and pins Go 1.25.13 for govulncheck. Physical dual-platform acceptance FAILED (macOS 38/44, Windows 38/44; remaining product defect Windows inspect JSON not_installed); this candidate does not authorize stable v0.4.0. Tagged implementation. | |
| v0.4.0-rc.7 | Unchanged from v0.4.0-rc.6: inclusive Claude Code range 2.1.219–2.1.229. The Codex CLI range is unchanged at 0.133.0–0.147.0. | Seventh Phase 4 candidate after v0.4.0-rc.6 physical dual-platform acceptance FAILED. This candidate bounds Windows process listing, fails closed on determined out-of-range Claude (2.1.230) during read-only handoff, classifies hung --version as Compatibility UNTESTED instead of Runtime, and does not block source-only Grok preflight on missing native layout. Physical dual-platform acceptance FAILED (macOS 38/44, Windows 34/44; remaining product defect R1 off-PATH Inspect); this candidate does not authorize stable v0.4.0. Tagged implementation. | |
| v0.4.0-rc.6 | Unchanged from v0.4.0-rc.5: inclusive Claude Code range 2.1.219–2.1.229. The Codex CLI range is unchanged at 0.133.0–0.147.0. | Sixth Phase 4 candidate after v0.4.0-rc.5 physical dual-platform acceptance FAILED. This candidate remaps foreign/fixture-user workspaces only when the project leaf matches the cwd git repo, refuses a different-repository bind, and refuses non-TTY destination launch before index open. Dual-platform tagged-artifact acceptance is pending; this candidate does not authorize stable v0.4.0. Tagged implementation. | |
| v0.4.0-rc.5 | Unchanged from v0.4.0-rc.4: inclusive Claude Code range 2.1.219–2.1.229. The Codex CLI range is unchanged at 0.133.0–0.147.0. | Fifth Phase 4 candidate after v0.4.0-rc.4 physical dual-platform acceptance FAILED. This candidate kills hanging Windows --version process trees, refuses non-TTY destination launch before Plan, remaps foreign-OS and fixture-user workspaces onto the local git checkout, and classifies Codex compaction as summarized. Physical dual-platform acceptance FAILED; this candidate does not authorize stable v0.4.0. Tagged implementation. | |
| v0.4.0-rc.4 | Unchanged from v0.4.0-rc.3: inclusive Claude Code range 2.1.219–2.1.229. The Codex CLI range is unchanged at 0.133.0–0.147.0. | Fourth Phase 4 candidate after v0.4.0-rc.3 physical dual-platform acceptance FAILED. This candidate treats an explicit empty dest home as supported, bounds hanging --version probes including grandchild-held pipes, persists --no-launch without warning acks, keeps sidecared summarized fidelity, and fixes Windows passphrase-FD / isolation-env unit failures. Physical dual-platform acceptance FAILED; this candidate does not authorize stable v0.4.0. Tagged implementation. | |
| v0.4.0-rc.3 | Unchanged from v0.4.0-rc.2: inclusive Claude Code range 2.1.219–2.1.229. The Codex CLI range is unchanged at 0.133.0–0.147.0. | Third Phase 4 candidate after v0.4.0-rc.2 physical dual-platform acceptance FAILED. This candidate carries C4 (wrong-repo cwd refused), F8 (non-TTY fail-closed before spawn), Grok-source busy-check, R4 timed-out probe classified UNTESTED/Compatibility, plus remaining matrix product defects (--no-redact, list isolation, fidelity/projection_events, checkpoint sidecar refs, destination MCP/skill gaps). Physical dual-platform acceptance FAILED; this candidate does not authorize stable v0.4.0. Tagged implementation. | |
| v0.4.0-rc.2 | Widened the inclusive Claude Code range from 2.1.219–2.1.228 to 2.1.219–2.1.229. The Codex CLI range is unchanged at 0.133.0–0.147.0. | Second Phase 4 candidate. v0.4.0-rc.1 physical acceptance FAILED, and this candidate fixes what it found: Claude-sourced handoffs no longer depend on a version file real installs never create, reader-emitted paths are tokenized before capsule validation, live changed files reach the destination, a timed-out version probe is classified UNTESTED instead of accepted, and capsule validation checks path-typed fields instead of rejecting prose that starts with a slash. Physical dual-platform acceptance FAILED; this candidate does not authorize stable v0.4.0. Tagged implementation. | |
| v0.4.0-rc.1 | Widened the inclusive Claude Code range from 2.1.219–2.1.227 to 2.1.219–2.1.228. The Codex CLI range is unchanged at 0.133.0–0.147.0. | First Phase 4 candidate: explicit structured handoff of the same task into a new Claude Code or Codex session. Gemini CLI, OpenCode, and Grok Build are handoff sources only. The 2.1.228 patch is source-tested only, and dual-platform tagged-artifact acceptance is pending; this candidate does not authorize stable v0.4.0. Tagged implementation. | |
| v0.3.0 | Claude Code 2.1.219–2.1.227 and Codex CLI 0.133.0–0.147.0 unchanged from RC7. | Stable Phase 3 release after dual-platform tagged-artifact acceptance PASS on v0.3.0-rc.7. Fresh stable dual validation is required after tag publication. Tagged implementation. | |
| v0.3.0-rc.7 | Claude Code 2.1.219–2.1.227 and Codex CLI 0.133.0–0.147.0 unchanged from RC6. | Packages the post-RC6 Phase 3 harden stack (non-TTY fail-closed native launch, Windows Ctrl+C safety, capability probe demotion, isolated CLAUDE_CONFIG_DIR/CODEX_HOME roots, expanded local smoke) without widening Claude Code 2.1.219–2.1.227 or Codex CLI 0.133.0–0.147.0. Tagged-artifact acceptance is pending. Tagged implementation. | |
| v0.3.0-rc.6 | Expanded the inclusive Claude Code range from 2.1.219–2.1.220 to 2.1.219–2.1.227 and the Codex CLI range from 0.133.0–0.146.0 to 0.133.0–0.147.0. | Widened fail-closed product ranges so primary-host Claude Code 2.1.225/2.1.227 and Codex CLI 0.147.0 installs were SUPPORTED for dual-platform Phase 3 retest. Dual-platform tagged-artifact acceptance failed on real-launch baseline, TTY/picker, and related host evidence rows. Tagged implementation. | |
| v0.3.0-rc.5 | No agent-version range change documented. | Carries the RC4 Windows-first product fixes and makes PowerShell release-artifact verification portable without widening Claude Code 2.1.219–2.1.220 or Codex CLI 0.133.0–0.146.0. Tagged-artifact acceptance is pending. Tagged implementation. | |
| v0.3.0-rc.4 | No agent-version range change documented. | Fixes the RC3 native-Windows PowerShell 5.1 staging and human-output privacy blockers without widening Claude Code 2.1.219–2.1.220 or Codex CLI 0.133.0–0.146.0. Its release workflow failed before publication. Tagged implementation. | |
| v0.3.0-rc.3 | No agent-version range change documented. | Hardens Windows trusted executable resolution and PowerShell snapshot/staging gates after RC2 native Windows FAIL without widening Claude Code 2.1.219–2.1.220 or Codex CLI 0.133.0–0.146.0. Native Windows acceptance still failed on later staging/privacy gates. Tagged implementation. | |
| v0.3.0-rc.2 | No agent-version range change documented. | Corrects Windows trusted executable resolution for extensionless vendor names via PATHEXT without widening Claude Code 2.1.219–2.1.220 or Codex CLI 0.133.0–0.146.0. Tagged-artifact acceptance is pending. Tagged implementation. | |
| v0.3.0-rc.1 | No agent-version range change documented. | Adds Phase 3 verified-resume observation and authorization without widening the Claude Code 2.1.219–2.1.220 or Codex CLI 0.133.0–0.146.0 ranges. macOS acceptance passed; native Windows failed. Tagged implementation. | |
| v0.2.0 | No agent-version range change documented. | Ships the RC2-tested runtime adapter tree unchanged. Apple Silicon macOS and native Windows x64 are verified stable platforms; Intel macOS and Linux/WSL2 artifacts remain preview until their deferred physical acceptance completes. Tagged implementation. | |
| v0.2.0-rc.3 | No agent-version range change documented. | No adapter behavior change from v0.2.0-rc.2. This candidate adds verified package-manager distribution metadata and native package artifacts without widening the tested Claude Code or Codex CLI ranges. | |
| v0.2.0-rc.2 | No agent-version range change documented. | No adapter behavior change from v0.2.0-rc.1. This candidate corrects release-artifact provenance and native-Windows verification without widening the tested Claude Code or Codex CLI ranges. | |
| v0.2.0-rc.1 | Expanded the inclusive Codex CLI range from 0.133.0–0.145.0 to 0.133.0–0.146.0; the Claude Code range remains 2.1.219–2.1.220. | Codex CLI 0.146.0 passed the complete Phase 2 physical matrix on both macOS and native Windows. The adapter still fails closed for stable versions above 0.146.0 and for every prerelease. Tagged implementation. | |
| v0.1.0 | No agent-version range change documented. | No behavior change from v0.1.0-rc.8. The stable release ships that candidate’s product code unchanged, so the two-device Phase 1 acceptance evidence applies directly to it. Tagged implementation. | |
| v0.1.0-rc.8 | No agent-version range change documented. | Restore liveness no longer depends on an open file handle. Claude Code closes its session file between appends, so a live session held no handle and RC7 treated it as free. Detection now also matches an agent naming the exact session on its command line, or working inside the session’s mapped project. Tagged implementation. | |
| v0.1.0-rc.7 | No agent-version range change documented. | Restore liveness detection became session-scoped. A restore now checks whether the exact target session file is held open, using operating-system file handles, instead of asking whether any Claude Code or Codex process is running. A session that is genuinely in use is restored alongside the live one rather than refused. Tagged implementation. | |
| v0.1.0-rc.6 | No agent-version range change documented. | Codex working directories resolve to canonical project IDs. Additional-device init changed from RC5’s metadata-only manifest probe to reading the complete remote ciphertext; init still does not decrypt it or validate the passphrase. Tagged implementation. | |
| v0.1.0-rc.5 | No agent-version range change documented. | Additional-device init required a metadata-only existence probe for the remote manifest before saving local setup; it did not read or decrypt the ciphertext. Tagged implementation. | |
| v0.1.0-rc.4 | No agent-version range change documented. | Claude restore paths became destination-aware, legacy unmapped snapshots fail closed, and exact native restore locations are verified. | |
| v0.1.0-rc.3 | Introduced the current inclusive ranges: Claude Code 2.1.219–2.1.220 and Codex CLI 0.133.0–0.145.0. | Installed versions outside a tested stable range become UNTESTED and setup check exits with compatibility code 5. | |
| v0.1.0-rc.2 | No agent-version range change documented. | Release CI corrected signed-tag verification; no adapter compatibility change is recorded. | |
| v0.1.0-rc.1 | Claude Code and Codex adapters launched with fixture-backed checks, but this changelog does not publish an exact historical version range. | Established fail-closed adapter compatibility states and same-vendor session restore. |
“No change documented” is intentional. It means the tagged changelog does not claim a range change; it does not reconstruct private test history or guess what an earlier binary accepted. RC1 and RC2 do not publish exact historical endpoints in the current release evidence, so this tracker leaves them unstated.
How a range changes
- A vendor version is exercised against deterministic synthetic adapter fixtures.
- Discovery, structural path handling, export, restore, exclusions, and failure behavior are reviewed.
- The adapter constants and tests change together.
compatibility.json, documentation, and release notes cite the exact evidence.- Physical platform results remain separately qualified until their acceptance rows pass.
A new vendor release is not supported merely because its version number is close to the current range. The range expands only after evidence is committed and released.
Before upgrading an agent
- Check this tracker and the current compatibility matrix.
- Keep the existing agent and Reinstate installers or another recovery path.
- Run
rein setup checkbefore any push or pull. - Use a synthetic, non-sensitive session for a newly accepted version.
- Report the exact agent version, Reinstate version, operating system, and redacted failure.