Skip to main content
The Sessions tab on a coding agent’s detail page lists every individual coding session for that vendor, one row per coding_agent.session.id (folded up to its chat thread when subagents are linked in). Claude Code sessions sent only through its native telemetry, with no OpenLIT hook, appear here too, keyed by Claude Code’s session.id. They need native traces switched on (CLAUDE_CODE_ENHANCED_TELEMETRY_BETA=1 and OTEL_TRACES_EXPORTER=otlp), and their cost comes from Claude Code’s api_request log events, so it also needs OTEL_LOGS_EXPORTER=otlp. Native telemetry doesn’t report the repository, working folder, code changes or outcome, so those columns stay empty unless the hook also runs.

Sessions list

Columns: Session, User, Started, Duration, Model, Tool calls, Code changed (+added/-removed, with accepted/rejected broken out in a tooltip), Acceptance %, Commits, Pull Requests, Tokens, Cost, and Outcome.

Session detail

Clicking a session opens the same trace detail view used for Traces, rooted at that session. It defaults to the Chat view since a conversational read fits an IDE/CLI session better than a span tree - you’ll see prompts, tool calls, and edits laid out like a transcript, with the AI Analysis, Timeline, and Graph views still available if you want a different angle. The header adds session-specific meta pills on top of the usual Duration, Tokens, Cost, and Model stats: Coding Agent (vendor), User, Working Folder, Repository, Branch, Terminal, Commits, Lines added/deleted, Acceptance, Pull Requests, and Outcome. Use Prev / Next to step through sessions without returning to the list.
If a session was captured under the minimal or metadata_only content-capture mode, the detail view shows a banner explaining that prompt bodies and tool I/O weren’t recorded for that session - see Privacy & Governance.

Analytics

Zoom back out to vendor-wide trends and breakdowns