Reinstate
Install

Integration · Kimi Code CLI · T2

Kimi Code CLI as a T2 Handoff Source | Reinstate

Kimi Code CLI is T2: a handoff source and a read-only local index. Reinstate does not launch Kimi as a native resume target and does not sync Kimi sessions.

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

Kimi Code CLI support at a glance

Tier
T2 Handoff source
Release
Stable v0.6.0 (native Windows x64 certified, macOS deferred #403)
Storage family
F1 home tree
Native resume (T3)
Not supported
Encrypted sync (T5)
Not supported

T2 means rein handoff --from kimi can build a portable capsule. Kimi Code CLI is not a T3 resume agent and not a T5 sync agent.

What T2 includes

  • T1 read-only discovery, search, and inspect of local Kimi Code CLI sessions.
  • T2 structured handoff from Kimi Code CLI into a new Claude Code or Codex session.
  • Fail-closed behavior on an unrecognized layout (exit code 5).
  • Unknown wire.jsonl records stay referenced, with no payload body.

What T2 excludes

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

Native resume is same-vendor, and Kimi Code CLI is not a T3 agent.

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

Kimi's T2 handoff source ships in stable v0.6.0, certified by native Windows x64 tagged-artifact acceptance PASS under the single-platform waiver in ADR 0005 (Apple Silicon macOS acceptance deferred to #403). Earlier stable releases (v0.5.1 and before) predate this tier. See therelease boundary and the changelog.

Evidence

Dual-platform probes live under docs/testing/results/agent-probes. Fixtures live under testdata/sessionindex/kimi andtestdata/handoff/kimi. There is no T3 version probe and no T3 device report. See theKimi storage pageand the tier matrix.