100% browser-side analysis · No account
Find out why your AI coding session uses so many tokens.
Inspect Claude Code session logs for repeated reads, tool errors and growing context. Get a clear explanation, supporting evidence and practical next steps.
◇ Your logs stay in your browser◇ No API key required◇ Evidence-based findings
01 · IMPORT
Choose a session log
Claude Code JSONL is supported. Other agents may use different formats and are not yet supported.
Do not upload or share raw logs with others: they may contain prompts, file paths, source code or secrets. This tool does not transmit them.
02 · REVIEW
Session findings
SYNTHETIC EXAMPLE — these are generated test events, not your activity or measured savings.
Findings
Evidence & next steps
03 · ACTChoose a finding to view evidence.
A signal is not proof of unnecessary Token consumption. Cache tokens can have different pricing. We cannot determine vendor subscription-quota charges from session logs.
HOW IT WORKS
Three steps to a more understandable session
Import locally
Choose a Claude Code JSONL session file. Processing stays inside this page.
Inspect evidence
Review repeated file reads, retry patterns, tool errors and cache-read changes.
Take action
See cautious recommendations and export a report without prompt text or raw paths.