Reinstate
Install

Integration · Gemini CLI · T2

Gemini CLI as a T2 Handoff Source | Reinstate

Gemini CLI is T2: a handoff source and a read-only local index. Reinstate does not launch Gemini, does not write Gemini session files, and does not sync Gemini sessions. T-050 left Gemini at T2.

Last verified
Current release
v0.6.0
Release status
v0.6.0 stable · native Windows x64 tagged-artifact acceptance PASS (215/215 required rows, docs/testing/results/2026-09-09-windows-v060rc8.md) under the single-platform waiver (ADR 0005) · Apple Silicon macOS acceptance deferred to #403 · supersedes v0.5.1

Gemini CLI support at a glance

Tier
T2 Handoff source
Storage family
F1 home tree
Native resume (T3)
Not supported
Encrypted sync (T5)
Not supported

T2 means rein handoff --from gemini can build a portable capsule from a local Gemini CLI thread. T3 verified resume needs a fail-closed version range and dual-platform physical resume journeys. Those are not committed, so Gemini stays T2.

What T2 includes

  • T1 read-only discovery, search, and inspect of local Gemini CLI sessions.
  • T2 structured handoff from Gemini CLI into a new Claude Code or Codex session.
  • Fail-closed behavior on an unrecognized layout (exit code 5).

What T2 excludes

  • No rein resume / rein fork of a Gemini session.
  • No rein handoff --to gemini destination.
  • No rein push / rein pull of Gemini sessions.
  • No write into Gemini’s session store.

Native resume is same-vendor, and Gemini is not a T3 agent.

A handoff starts a new Claude Code or Codex session. It does not reconstruct Gemini history or translate the vendor transcript.

Evidence

Committed fixtures live under testdata/sessionindex/gemini andtestdata/handoff/gemini. A Windows physical path exists; there is no dual-platform T3 resume report. See theGemini storage pageand the tier matrix.