I built this because my own Claude Code spend didn't match what my tracker said. Turns out it reads session logs, which don't carry real cost. So I made one that reads the statusline β the source behind the bill. Run wtclaude compare and tell me your gap. Mine was not small.
Your Claude Code cost tracker is probably wrong.
Most read session logs. Logs don't carry billing-grade cost β so the number drifts from your actual bill.
WTClaude reads the statusline instead: the same source behind your bill.
It's free + open source. Here's what it does π§΅
Bracing for the June 15 Claude billing change? It was paused β didn't take effect. Agent SDK, claude -p & third-party still draw from your subscription as before. No credit to claim. You can exhale.
One command shows what your Claude Code spend really is:
wtclaude compare β your billing-grade cost next to the number a log-based tracker reports, and the gap between them. Now per-pool after the June 15 split.
Free + open source: https://t.co/wn2GdxJHIB
Two Claude billing changes, 8 days apart: the June 15 Code split, then the June 23 Fable cliff. People keep mixing them up β so I mapped what changes, and when. No drama.
Posted my zero-to-launch story on @IndieHackers today: I shipped a free, billing-grade Claude Code cost tracker β built because my own tracker never matched my bill.