Reinstate
Install

Integration · OpenAI Codex CLI · T5

Sync Codex CLI Sessions Across Devices | Reinstate

Codex CLI is T5: encrypted same-vendor session sync plus T3 native resume. Reinstate rewrites the structural working directory for the destination project and preserves Codex’s native date-partitioned rollout layout. Codex-to-Codex only.

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

Codex CLI support at a glance

Tier
T5 Encrypted sync
Session direction
Codex CLI → Codex CLI
Tested stable range
0.133.0–0.149.0
Primary platforms
macOS and native Windows
Remote storage
Your S3-compatible or Cloudflare R2 bucket

Stable v0.5.1 accepts Codex CLI 0.133.0–0.149.0; the ceiling moved to 0.149.0 on dual-platform physical resume evidence. Dual-platform tagged-artifact acceptance PASS covers Apple Silicon macOS and native Windows x64. Intel macOS and WSL2 are optional and unverified. A version outside the range is UNTESTED; Reinstate permits read-only discovery but refuses export and restore.

How Codex session sync works

Codex stores the source working directory in each rollout's structuralsession_meta.cwd. That path identifies the local checkout, so it cannot be copied literally when the destination machine uses a different root.

  1. Configure a canonical project ID and the actual local project root on each device.
  2. During discovery, Reinstate resolves session_meta.cwd to that project ID and excludes rollouts outside mapped roots.
  3. Export replaces the resolved source root with a portable$${REPO:<id>} token, then encrypts the artifact locally.
  4. Restore expands the token through the destination device's project mapping while preserving Codex's native date-partitioned rollout structure.

Structural paths are portable; transcript prose is not rewritten.

Reinstate changes known path fields needed for native resume. It deliberately leaves free-form prompts, responses, and unknown fields alone rather than modifying the meaning of the conversation.

Security boundary

Reinstate reads local Codex session files and does not call OpenAI APIs or require OpenAI account credentials. Authentication files, API keys, OAuth tokens, credential stores, caches, and regenerable dependencies are excluded from sync. Storage credentials stay in the operating system keyring.

Session content is encrypted locally with age passphrase encryption before upload. Because a transcript may contain sensitive text produced during a coding task, read thesecurity model and threat boundaries before using real sessions.

Current limitations

  • Codex rollouts can be resumed only by Codex in Phase 1.
  • Rollouts outside configured canonical project roots are not exported.
  • Untested or unsupported Codex versions cannot be pushed or pulled.
  • Credentials, MCP servers, skills, plugins, hooks, and agent settings are not synced.
  • WSL1 is unsupported; native Windows and WSL2 are separate Reinstate devices.
  • Reinstate is independent of OpenAI and is not an official Codex product.

Start with Codex

Install the stable release and configure the same canonical project ID on each machine. Push the selected session on the source, inspectrein pull --agent codex --session SESSION_ID --dry-run on the destination, then restore that scoped session and use Codex's native resume command.