Privacy
Browser only
The file is parsed in your browser. The page has no upload endpoint and no account flow.
Free browser tool
Claude Code Session Log Viewer
Drop a Claude Code JSONL transcript and turn it into a readable local timeline of messages, tool calls, tool results, and token fields.
Parser stance
Known fields + unknowns
The viewer reads common Claude Code transcript shapes and reports unknown records instead of dropping them silently.
Records0
Tool uses0
Tool results0
Parse errors0
Select a transcript to build a readable timeline.
FAQ
Does the log viewer upload my transcript?
No. The File API reads the selected JSONL file inside your browser. The site does not send transcript content to a server.
Why does the viewer show unknown records?
Claude Code transcript entries are internal and can change. Unknown records are preserved as metadata so parser drift is visible.
Related evidence
Free tool
Token Analyzer
Estimate Claude Code transcript token usage and cost by turn with a dated model pricing table and CSV export.
Free tool
Audit Checklist
Run an interactive agent-session audit checklist and export a concise Markdown note for PRs, incidents, and handoffs.
Telemetry
Observability
A practical map of Claude Code and Agent SDK telemetry: traces, metrics, logs, identity attributes, and event analysis.
Controls
Hook Audits
How Claude Code hooks create reliable capture points for prompts, tool calls, stop events, subagents, and policy decisions.
Governance
Storage
How to design Claude transcript storage, SessionStore mirroring, retention windows, and deletion workflows without losing useful evidence.