Rye records local evidence from multiple sources:
- Model requests and responses observed by the proxy or API shim.
- Policy decisions for intercepted requests.
- Wrapped process session start and end events.
- File changes observed during wrapped sessions.
- Approval events detected from supported terminal output.
- Assistant history ingested from local transcript stores.
Inspect proxy history
Show recent captured traffic:
Filter by domain:
Filter by method:
Limit results:
Export history
Export structured JSON:
Export a domain-specific window:
History exports can include prompts, source code, tool output, headers, and model responses. Store and share them as sensitive data.
Inspect approvals
Show recent approval events:
Limit output:
Approval events help you understand when a user granted one-time approval, created a persistent rule, or later executed a command under a persistent rule.
Assistant history ingestion
Rye can ingest local assistant history in the background. This is enabled by default when the proxy starts.
The ingester scans sources such as:
- Claude Code transcripts under
~/.claude/projects/.
- Codex CLI rollout files under
~/.codex/sessions/.
- Cursor session and workspace state.
It tracks byte offsets, chunks large JSONL content safely, hashes chunks, skips already-uploaded content, and uploads new data over gRPC.
Disable ingestion for a proxy session:
Local retention
Rye keeps a local SQLite store for cached traffic, events, policy snapshots, and ingestion checkpoints.
Default retention:
- Delete data older than 7 days.
- Keep the database under 512 MB when possible.
- Check retention once per hour.
Retention protects the local workstation. It does not replace your organization’s data handling policy for exported files or centralized audit data. 
