The session detail panel

The session detail panel is where Claude Session Monitor packs in the most information. Click any session in the sidebar and a themed panel opens on the right, bringing together the full transcript, tool calls and sub-agent activity, and a token/context and cost breakdown — all in one view.

What the panel shows

The core is the session's full transcript — every turn between you and Claude, in order — so you don't scroll back through terminal history to reconstruct what happened. Interleaved with it are two more layers:

• Tool calls — every tool Claude invoked (reading/writing files, running commands…) shown inline in the order it happened, so you can trace exactly what each step did.
• Sub-agents — if the session spawned a sub-agent, its own execution is represented on its own terms, not flattened into the main conversation.

Token, context, and cost breakdown

The panel's other job is breaking down tokens and cost. The total token count uses this basis:

input + output + cache-write + cache-read

Counting cache-write and cache-read isn't arbitrary — it matches how cost is actually computed. If the panel only counted input and output, a cache-heavy session would show a token count that's a tiny fraction of what's billed, making the cost look inconsistent. Counting all four keeps token and cost consistent with each other.

The cost figure is an estimate computed from each model's own pricing (including separate cache-write and cache-read rates). It won't match your invoice to the cent, but it's accurate enough to see roughly what a session cost and which token category drove it.

The panel remembers what you had open

Reload the VS Code window and the detail panel you had open — along with the dashboard, if it was open — is restored automatically. No need to return to the sidebar and re-open the session.