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
- 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
- Owner
- Harjot Singh Rana
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.jsonllogs. - 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 forkof a Copilot session. - No structured handoff from or to GitHub Copilot CLI.
- No
rein push/rein pullof Copilot sessions. - No write into Copilot’s session store.
- Not the retired
gh copilotextension, 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.