Compatibility

Reinstate Compatibility: Agents, Versions, and Operating Systems

The catalog names eighteen coding agents. Encrypted sync (T5) covers Claude Code, Codex CLI, and OpenCode. Grok Build and Qwen Code are T4 handoff destinations with same-vendor native resume. Gemini CLI and Kimi Code CLI are T2 handoff sources. Four more are T1 read-only, and seven are T0: named, with a reason they are not usable. Native resume stays same-vendor.

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

Support is a tier, not a yes-or-no flag

T5 is encrypted same-vendor sync. T2 is a handoff source. T0 is a named agent thatrein doctor --agents can explain. A T0 row is not an integration. Native resume stays same-vendor. Cross-agent work is an explicit portable handoff into a new Claude Code or Codex session.

Catalog agent support tiers T0 through T5
AgentFamilyT0KnownT1DiscoverT2Handoff sourceT3Verified resumeT4Handoff destinationT5Encrypted syncEvidence
Claude CodeT5F1Home treeYesYesYesYesYesCurrentEvidence
OpenAI Codex CLIT5F1Home treeYesYesYesYesYesCurrentEvidence
Gemini CLIT2F1Home treeYesYesCurrentEvidence
OpenCodeT5F3Embedded DBYesYesYesYesYesCurrentEvidence
Grok BuildT4F1Home treeYesYesYesYesCurrentEvidence
Kimi Code CLIT2F1Home treeYesYesCurrentEvidence
PiT1F1Home treeYesCurrentEvidence
Qwen CodeT4F1Home treeYesYesYesYesCurrentEvidence
Cursor CLIT1F1Home treeYesCurrentEvidence
ClineT1F1Home treeYesCurrentEvidence
Roo CodeT0F3Embedded DBlayout unverifiedEvidence
AiderT0F4Project filelayout unverifiedEvidence
GitHub Copilot CLIT1F1Home treeYesCurrentEvidence
AmpT0F5Remoteserver-backed historyEvidence
OpenHandsT0F5Remoteserver-backed historyEvidence
ZCodeT0F5Remotedesktop-only distributionEvidence
MiniMaxT0F5Remotelayout unverifiedEvidence
Antigravity CLIT0F1Home treelayout unverifiedEvidence

Machine-readable status was last reviewed on . The same records are available as machine-readable JSON. Fixture evidence is pinned to commitcf6e430f3aa7. T0 rows have no last-tested date: the evidence is the descriptor and storage page, not a probe.

Tested version ranges

AgentTierTested stable rangeResume modeLast tested
Claude CodeT52.1.2192.1.263Claude Code to Claude Code (T5 encrypted sync; T3 same-vendor resume)
Test source
OpenAI Codex CLIT50.133.00.149.0Codex to Codex (T5 encrypted sync; T3 same-vendor resume)
Test source
Gemini CLIT20.55.10.55.1Handoff source only (T2); no native resume
Test source
OpenCodeT51.18.211.18.29OpenCode to OpenCode (T5 encrypted sync; T3 same-vendor resume and fork); OpenCode as a structured handoff destination (T4)
Test source
Grok BuildT41.0.51.0.13Same-vendor native resume via grok --resume <uuid> (T3); handoff destination via grok --session-id <uuid> (T4)
Test source
PiT10.73.10.73.1Not usable (T1 discover only)
Test source
Qwen CodeT40.21.120.23.0Qwen Code to Qwen Code (T3 same-vendor resume and fork); Qwen Code as a structured handoff destination (T4)
Test source

Every agent with a fail-closed version range is listed here, whatever its tier — T5 encrypted sync, T4 handoff destination and native resume, T2 handoff source, or T1 discovery. Ranges reflect current source compatibility evidence and deterministic synthetic fixtures; they are not a claim that every platform row has passed physical-device certification. Prereleases and versions outside each inclusive range are UNTESTED. Theagent-version change tracker records when the inclusive ranges and fail-closed behavior changed across releases.

Operating-system matrix

EnvironmentClaude CodeCodex CLIReinstate statusEvidence
macOS native · arm64RequiredRequiredStable Verified
Evidence and gate
macOS native · amd64Preview UnverifiedPreview UnverifiedPreview UnverifiedNo completed result
Evidence and gate
Windows 11 native · amd64RequiredRequiredStable Verified
Evidence and gate
Windows 11 WSL2 · amd64Preview UnverifiedPreview UnverifiedPreview UnverifiedNo completed result
Evidence and gate

What the compatibility states mean

Supported
Exact layout and version range has release evidence; discovery, push, and pull proceed.
Untested
Recognizable but unverified; discovery is read-only and writes fail closed.
Unsupported
Known-incompatible layout, version, environment, or agent; the operation stops.
Not installed
No local installation or session root found; reported as informational.

rein setup check returns compatibility exit code 5 when an installed adapter is UNTESTED or UNSUPPORTED. Phase 1 has no unsafe compatibility override. Unknown layout is exit code 5, never a best-effort parse.

How cross-platform path compatibility works

Reinstate rewrites known structural paths to portable tokens such as$${HOME} and $${REPO:<id>}. The destination device expands those tokens using its own configured paths. The internal mapper's work-alias primitive is not wired into Reinstate configuration or adapters. Free-form transcript prose and unknown fields are left unchanged.

Native Windows and WSL2 are separate devices.

Do not point both environments at one shared agent-state directory. Their path semantics and vendor layouts differ, so each must have its own Reinstate device identity and mappings.

Explicitly unsupported

  • WSL1.
  • Treating native Windows and WSL as one Reinstate device.
  • Automatically sharing one agent-state directory between Windows and WSL.
  • Exporting or restoring an untested agent layout.
  • Encrypted sync for any agent other than Claude Code, Codex CLI, and OpenCode (T5 only).
  • Native resume for T2 handoff sources or T0 catalog names.
  • Silent translation between vendor-native transcripts.
  • Syncing vendor credentials, raw secrets, MCP settings, skills, or plugins.

Verify your own device

Run rein setup check before pushing real sessions. Treat its state as authoritative for the installed version and local layout, and review the repository's compatibility evidence when a vendor ships a new version.