Integration

Gemini CLI session files: what they contain

Local OpenTelemetry output

Supported data

Prompts, tools, model routing, durations, and token fields depend on telemetry configuration.

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 Gemini CLI export can tell you

Prompts: Available; Counted from user events, or from the user messages in a local session snapshot.
Responses: Available; Counted from model events, or from the model messages in a local session snapshot.
Tool calls: Available; Counted from tool invocation events and from tool parts in a snapshot. A snapshot is a complete message list, so seeing none there is a proven zero.
Agents launched: Not in export; Neither Gemini CLI telemetry nor a local session snapshot records subagent launches, so the count is never claimed for this source.
Tokens: Sometimes; Read from telemetry usage when prompt logging is off and usage is exported. Local session snapshots carry no usage, so a snapshot-only import leaves 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: Sometimes; Telemetry names the model that served each turn. A local session snapshot does not.
Summed session span: Available; First to last event instant in the session.
AI active time: Sometimes; Read from telemetry turn durations when they are present. A snapshot-only import has none.
Estimated interaction time: Sometimes; Computed only when the source reports no real turn duration, so it never sits beside a measured AI active time for the same session.
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.