Integration · GitHub Copilot CLI · T1

GitHub Copilot CLI as a T1 Discover Agent | Reinstate

GitHub Copilot CLI is T1: a read-only local index. Reinstate does not launch Copilot as a native resume target, does not use it as a handoff source or destination, and does not sync Copilot sessions.

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

GitHub Copilot CLI support at a glance

Tier
T1 Discover
Storage family
F1 home tree
Native resume (T3)
Not supported
Encrypted sync (T5)
Not supported

T1 means rein sessions --agent copilot, search, and inspect work against local GitHub Copilot CLI sessions. Resume and fork stay refused.

What T1 includes

  • Read-only discovery, search, and inspect of local session-state/*/events.jsonl logs.
  • Fail-closed behavior on an unrecognized first-record shape.
  • SQLite sidecars (session.db, session-store.db) are not parsed.

What T1 excludes

  • No rein resume / rein fork of a Copilot session.
  • No structured handoff from or to GitHub Copilot CLI.
  • No rein push / rein pull of Copilot sessions.
  • No write into Copilot’s session store.
  • Not the retired gh copilot extension, and not editor Copilot chat.

Native resume is same-vendor, and GitHub Copilot CLI is not a T3 agent.

Evidence

Dual-platform probes live under docs/testing/results/agent-probes. Fixtures live under testdata/sessionindex/copilot. There is no T3 device report. See theCopilot storage pageand the tier matrix.