Read the evidence grade
Supported means a named implementation and deterministic evidence exist for the stated scope. Limited means partial fidelity or conditional support. Unavailable means no verified adapter for that operation. Unknown means missing evidence, never zero activity or implicit permission.
This matrix describes reviewed pre-release source, not installed-version parity, provider policy or live account readiness. Local means the Commandem local adapter, not an arbitrary provider CLI running on your machine.
Core conversation capabilities
| Operation | Claude | Codex | Gemini | Antigravity | Local |
|---|---|---|---|---|---|
| List/view owned history | Supported | Supported | Supported | Unavailable; native archives are not imported | Supported, default namespace |
| Named-account archives | Supported | Supported | Supported | Unavailable; named Profiles are disabled | Unavailable |
| Native owned-session resume | Supported | Supported | Supported | Supported with a known conversation ID; no archive picker | Supported, default namespace |
| Trace / Replay fidelity | Limited; richer tool events | Limited; bounded tool inputs and output bodies, execution status unknown | Limited; bounded saved tool inputs and exact response-body observations, execution status unknown | Unavailable for native archives | Limited |
| Verified multi-turn Incognito | Supported; artifact purge scope applies | Unavailable in the reviewed adapter | Unavailable in the reviewed adapter | Unavailable in the reviewed adapter | Unavailable |
| Automatic continuity | Supported within owned paths | Limited; identity checked, classification gaps | Limited; identity checked, classification gaps | Limited; exact active conversation ID | Limited; default namespace |
Codex archive evidence: Trace and Replay retain saved function/custom tool inputs and output bodies from the selected Profile, project and session. A result links to a call only when its nonempty ID identifies a unique preceding call in admitted evidence. Missing, duplicated, malformed or unsupported records remain explicit gaps; output text does not prove execution success, failure or duration. Reads cover the first 8 MiB and at most 2,000 events, with overlong lines and text explicitly limited. This is deterministic archive/CLI evidence, not complete native-tool or live-provider certification.
Gemini archive evidence: Trace and Replay retain saved tool-call inputs and matching saved response bodies from the selected Profile, project and session. A response links only when its nonblank call ID and exact tool name identify one unique preceding call in complete admitted evidence. Saved status, response prose and completion timestamps do not prove execution success, failure or duration. Message-ID replacements, whole-message snapshots and target-inclusive rewind select current saved evidence; missing, duplicated, malformed, unsupported or bounded evidence keeps explicit gaps and cannot establish a unique result attribution. The selected read covers at most 8 MiB, 1 MiB per JSONL line and 2,000 folded messages; projection retains at most 2,000 events and 8,000 runes per text field. These are selected-read and projection limits, not an aggregate discovery or whole-archive resource guarantee. Deterministic local archive/CLI evidence does not certify live Gemini execution, complete native-tool coverage, unseen writers, History/Matrix behavior or privacy parity.
Usage is a separate evidence surface
- Claude: account-scoped cached rate-limit events can provide reported windows. Absent or old observations are not real-time headroom.
- Codex: a read-only account quota RPC can provide account-specific windows; failed or unsigned-in profiles remain unknown.
- Gemini: activity and exhaustion observations are available, not a complete quota-percentage meter.
- Antigravity: native usage is conversation-cumulative. The adapter leaves turn-level usage unavailable; it does not present a quota-percentage meter.
- Local/API: server telemetry and receipt accounting vary. Estimated transcript value and subscription quota are not interchangeable.
The generic parity baseline and newer fleet-usage implementation cover different scopes; this page deliberately does not repeat the older baseline's blanket quota limitations as current fact.
Handoff and privacy are not parity shortcuts
Cross-provider transfer is reviewed context delivery, not foreign native resume. Inspect provenance and privacy before a handoff. Unknown training/retention controls remain unknown. Incognito describes local/provider session persistence, not a promise about training.
Antigravity chat and its boundaries
The separate Antigravity adapter uses the native agy CLI. It streams replies and tool results, binds a fresh conversation to the selected project, and continues the exact conversation ID returned by that provider. A known ID can be passed to commandem chat <project> --agent antigravity --resume <conversation-id>; native archive listing and import are unavailable.
Default, Plan and Accept edits retain native sandboxing. Tools that need approval depend on native Antigravity policy: the reviewed stream has no scoped approval-response channel. Full access is a separate explicit selection, never inherited from Claude's Guarded auto. Named Profiles are disabled because the adapter has no verified isolated account root. commandem model --agent antigravity --json reports the native model catalog as text when the account check succeeds; catalog access does not prove a chat or tool call will succeed.
Boundary and recovery: check native sign-in and policy when a tool is denied. Shared grants cannot resolve an Antigravity approval. Archive-based Trace, Replay and Matrix history do not gain Antigravity coverage from its live chat support; Incognito and turn-level usage remain unavailable.
Other adapters and integrations
Additional providers, API endpoints, tools and collaboration adapters have separate contracts. Their presence in a selector or catalog is not certification of history, quota, Incognito or two-way sync. Inspect the in-app capability details and unavailable states before dispatch. A deterministic fixture is not a live private-service smoke test.