Integration

Codex session files: what they contain

User-selected session log files

Supported data

Schema detection is used because local session layout is treated as versioned input.

Privacy

Raw prompts, responses, attachments, local paths, and source files stay on your device in either privacy mode. The only thing stats-with-titles adds is the conversation title.

Limitations

Provider export formats may change. Unknown fields are preserved as warnings instead of silently invented metrics.

Duplicate prevention

Re-imports use stable provider session identity and content normalization hashes. Container file checksums never define session identity.

Metric quality

Unavailable values remain null. Estimates are labelled estimated and exact values are never fabricated.

Troubleshooting

If detection fails, use the preview warnings and confirm the export source/version before importing again.

What a Codex export can tell you

Prompts: Available; Counted from user message events in the rollout file.
Responses: Available; Counted from assistant message events in the rollout file.
Tool calls: Available; Counted from tool, shell, and MCP invocation events, de-duplicated by call id.
Agents launched: Available; Counted from subagent start events in the rollout file.
Tokens: Sometimes; Read from the cumulative usage the rollout reports. Input includes cache reads for this source, which is why Codex and Claude Code token totals are not compared with each other. Older rollouts without usage leave tokens unavailable.
API-equivalent cost: Sometimes; Estimated from token counts against a dated public price list, and only when both the tokens and a known model rate are present.
Models: Available; Read from the model recorded on each event, so a session that switched models lists every one of them.
Summed session span: Available; First to last event instant in the session.
AI active time: Available; Read from the turn durations Codex reports when a turn completes or is aborted.
Estimated interaction time: Shown as AI active time; Not computed for Codex, which reports real turn durations. The gap estimate exists for sources that cannot measure the real thing.
User active time: Not in export; No export records how long you spent reading or typing. It could only be inferred by subtracting one estimate from another, and an inferred number shown as a measurement would be a fabrication.
Waiting time: Shown as AI active time; Waiting on the model is exactly the AI active time already shown. Repeating it under a second name would add a tile, not a measurement.
Project grouping: Available; Grouped by the Git remote or working directory recorded in the session, hashed before it leaves the browser.