Capture Paths
Mimir combines full proxy exchanges, bounded harness reconstructions, and lifecycle events into one session record. The available evidence depends on what the harness and provider expose.
| Traffic path | Durable evidence | Lifecycle | Searchable exchange |
|---|---|---|---|
| Redirected OpenRouter | Full redacted transport exchange | Capture events | Yes |
| Pi direct or subscription provider | Bounded reconstruction | Extension events | Yes, after persistence |
| OpenCode OAuth, subscription, or direct provider | Bounded reconstruction | Plugin events | Yes, after persistence |
| Claude Code, Codex, or Cursor hooks | Bounded prompt and response reconstruction | Hook events | Yes, after persistence |
| Hermes Nous, OAuth, or direct provider | Completed-turn summary | Plugin events | No |
| Other tools using Mimir proxy URLs | Full redacted transport exchange | Capture events | Yes |
Full proxy capture
Section titled “Full proxy capture”Redirected OpenRouter traffic preserves the complete redacted request and streamed response. The Worker stores the object in R2 and indexes searchable metadata in D1.
Reconstructed exchanges
Section titled “Reconstructed exchanges”Pi, OpenCode, Claude Code, Codex, and Cursor can report completed prompt and response fields exposed by their integration APIs. These are bounded reconstructions, not byte-for-byte provider transport archives.
Lifecycle-only evidence
Section titled “Lifecycle-only evidence”Harness events can keep a session current with turn summaries, heartbeats, titles, and session ends even when the underlying provider transport is not available. Hermes direct-provider traffic uses this path.
mimir session status <id> --json is authoritative for durable persistence.
Transport activity and scheduled capture responses are not proof that the
session was saved.