Reinstate
Install

Integration · OpenAI Codex CLI

Sync Codex CLI Sessions Across Devices | Reinstate

Reinstate syncs supported Codex CLI rollouts between configured devices, rewrites the structural working directory for the destination project, and preserves Codex’s native date-partitioned rollout layout. It supports Codex-to-Codex continuity only.

Last verified
Current release
v0.1.0-rc.8
Release status
pre-1.0 release candidate

Codex CLI support at a glance

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

The stated range is the current source compatibility evidence for macOS arm64 plus deterministic synthetic fixtures. Native Windows, macOS amd64, WSL2, and physical two-device acceptance remain release gates for stable v0.1. A version outside the range isUNTESTED; 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, RC8 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 release candidate 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.