Analyze your Claude Code session transcripts — token usage, productivity metrics, and insights. Free alternative to Rudel (HN #128).
Free alternative to Rudel (Claude Code Session Analytics)
100% local analysis • No data sent to external servers • Token estimates based on ~4 chars/token
Analyze Claude Code transcripts for token usage, topic mix, coding patterns, tools mentioned, and workflow signals so you can understand how sessions actually perform. This page is built for people who want a fast path to a working result, not a vague prompt-and-pray workflow. If you need a more reliable first draft, cleaner output, or a repeatable workflow you can hand to a teammate, Claude Code Analytics is designed to shorten that path.
Most visitors use Claude Code Analytics because they need something specific done now: a deliverable, a decision, or a workflow checkpoint. The sections below show the fastest way to get value from the tool and the adjacent pages that help you keep going.
Paste a Claude Code session transcript to turn a long conversation into clearer metrics and workflow insight.
Best for people who want to understand how coding sessions perform instead of relying on vague impressions.
Review how a coding session actually unfolded and where time or tokens went
Track patterns across prompting style, output, and session productivity
Use transcript analysis to improve shared workflows and training
A strong outcome from Claude Code Analytics is not just “some output.” It should be usable with minimal cleanup, aligned to the task you opened the page for, and specific enough that you can paste it into the next step of your workflow without rewriting everything from scratch.
If the first pass feels too generic, use the use cases, FAQs, and related pages here to tighten the scope. That usually produces better results faster than starting over in a blank chat.