CC Hubber

Your Claude Code usage, diagnosed. One command.

npx cchubber

Reads your local data, generates an HTML report. No API keys, no accounts. Sends anonymous stats for community benchmarks (details). Opt out: --no-telemetry.

Built during the March 2026 cache crisis because nobody could tell if they'd been hit. Thousands of users burning through limits 10-20x faster than normal, and Anthropic's only answer was "we're investigating." We wanted receipts.

What you get

A single HTML report that tells you three things: what you spent, why you spent it, and whether that's normal.

The diagnosis:

• Cache health grade (trend-weighted, recent 7 days count more)
• Inflection point detection: "Your efficiency dropped 3.2x starting March 17"
• Per-project cost breakdown with decoded project names
• Session intelligence: duration stats, tool usage, activity heatmap
• Model routing analysis (93% Opus? Your limits would last 3x longer on Sonnet)
• 8 actionable recommendations, each with estimated usage savings

The data:

• Cost calculated from actual token counts (LiteLLM pricing, not the broken costUSD field)
• Message-level deduplication (Claude Code JSONL files contain ~50% duplicates from session resume)
• Subagent visibility: Haiku and Sonnet background agents show up in model distribution
• CLAUDE.md section-by-section analysis with per-message cost impact
• Cache break estimation even when diff files don't exist on your CC version

The shareable card: An animated card with your grade, spend, cache ratio, and diagnosis line. Export as video. Post it. Let people see the numbers Anthropic won't show them.

Install

npx cchubber

Or globally:

npm install -g cchubber
cchubber

Node.js 18+. Works on macOS, Windows, Linux.

The cache bug (March 2026)

Between v2.1.69 and v2.1.89, five things broke at once:

1. A sentinel replacement bug in Anthropic's custom Bun fork dropped cache read rates from 95% to 4-17%
2. The --resume flag caused full prompt-cache misses on every single resume
3. One session generated 652,069 output tokens with zero user input ($342 gone)
4. Peak-hour throttling kicked in for 7% of users without announcement
5. A 2x off-peak promotion expired, making the baseline feel like a cut

v2.1.90 fixes most of these. Run claude update.

CC Hubber shows you whether you were affected. If your report has a sharp inflection point around mid-March, that's probably when it hit you.

What the community figured out

These tips came from GitHub issues, Reddit threads, and Twitter during the crisis. CC Hubber's recommendations are based on this data.

• Start a fresh session for each task. Long sessions bleed tokens.
• Route subagents to Sonnet (model: "sonnet" on Task calls). Same quality, 5x cheaper per token.
• Keep your CLAUDE.md under 200 lines. It gets re-read on every message. 12K tokens at 200 messages/day costs $1.23/day cached.
• Run /compact every 30-40 tool calls. Context bloat compounds.
• Create a .claudeignore file. Exclude node_modules/, dist/, *.lock. Saves tokens on every context load.
• Avoid --resume on older versions. Fixed in v2.1.90.
• Shift heavy work (refactors, test generation) outside 5am-11am PT. That's when Anthropic throttles session limits.

How the cost works

Claude Code doesn't show costs for Max and Pro plans (costUSD is always 0). CC Hubber calculates equivalent API cost from your token counts using LiteLLM's pricing data.

The number you see is what you'd pay on the API tier for the same usage. Useful for comparing consumption across days and projects. Not a billing statement.

Data sources

Everything is local. CC Hubber reads files that already exist on your machine.

| Source | Path | What it contains | |--------|------|-----------------| | Conversations | ~/.claude/projects/*/ | Token counts per message, per model | | Subagents | ~/.claude/projects/*/subagents/ | Haiku/Sonnet background agent usage | | Session meta | ~/.claude/usage-data/session-meta/ | Duration, tool counts, lines changed | | Cache breaks | ~/.claude/tmp/cache-break-*.diff | Why your prompt cache broke | | CLAUDE.md | ~/.claude/CLAUDE.md + project-level | File sizes, section breakdown, cost per message | | Rate limits | ~/.claude/.credentials.json | Live 5-hour and 7-day utilization |

Compared to ccusage

ccusage (12K+ stars) is great for cost accounting. It tells you what you spent.

CC Hubber tells you why, and whether it's normal. Inflection detection, cache break estimation, model routing savings, session intelligence, trend-weighted grading. Different tools for different questions.

Telemetry

CC Hubber sends anonymous usage stats once per day to power community benchmarks. This is what makes the leaderboard rank, grade calibration, and community comparisons in your recommendations work. Without it, every user gets the same generic thresholds instead of real benchmarks.

What's collected:

• Cache health: grade, ratio, hit rate, break count
• Cost: bucketed range (e.g. "$500-1K"), not exact amounts
• Models: opus/sonnet/haiku split percentages
• Sessions: count, average duration, tool usage counts
• Config: CLAUDE.md token count, hook count, MCP server names, skill count
• Environment: OS, architecture, Node version, Claude Code version
• Tech stack: boolean flags (uses React, TypeScript, Tailwind, etc.)
• Anonymous machine ID (random hash, not tied to any account)

What's NOT collected:

• No file contents, project names, or directory paths
• No API keys, tokens, or credentials
• No conversation text or prompts
• No personal information (name, email, IP address)

Opt out anytime:

npx cchubber --no-telemetry
# or permanently:
export CC_HUBBER_TELEMETRY=0

Full source: src/telemetry.js

License

MIT

Credits

Built by @azkhh. Shipped fast with Mover OS.