Billing-grade accuracy
billing-gradeWTClaude reads the statusline data path — the same source behind your bill. Not broken logs, not estimates. Your real numbers.
Most Claude Code trackers estimate your cost from session logs — which can drift from your
bill. WTClaude reads the statusline instead: the same source behind your bill. So in your
terminal the number you see is billing-grade — run
wtclaude compare
and see your own gap.
npx wtclaude setup Free · MIT · macOS + Linux · ~60 seconds.
Most Claude Code trackers read JSONL session logs. Those logs record input tokens as 0 or
1 in about three-quarters of entries — they’re written mid-stream, before the response
finalizes, and never corrected. The result: the cost your tracker shows can drift from
what you actually spent — sometimes a little, sometimes a lot. A gap wide enough to choose
the wrong plan, miss a budget, or burn through agent credits without knowing. Run
wtclaude compare
to see yours.
The accuracy gap
Session-log estimate
estimate
reconstructed from the JSONL session logs
Billing-grade (your bill's source)
billing-gradeyour real cost
read from the statusline — the source behind your bill
Illustrative — your gap depends on your usage. Run wtclaude compare to see yours.
npx wtclaude setup → wtclaude compare WTClaude reads the statusline data path — the same source behind your bill. Not broken logs, not estimates. Your real numbers.
Built for the split (currently paused). If it returns, the dual-pool view lights up automatically — no reinstall.
Session timelines, daily debriefs, model breakdowns, and a “what-if” plan calculator.
wtclaude compare
shows your real number next to the broken one — the moment that changes how you think
about cost.
Claude Fable 5 is back: WTClaude tracks it
billing-grade in your terminal, and
wtclaude fable
forecasts what your pace would cost as usage credits after the July-7 allowance (a labeled
estimate; separate from the paused June-15 Agent-SDK change).
Sonnet 5 is the new Claude Code default. Fable 5 is back. Opus 4.8 is still there for the heavy lifting. WTClaude prices all three from your own real usage — so you choose on what it actually costs you, not the rate card.
The new default (in Claude Code v2.1.197 and on Free/Pro). We price it at $2/$10 — auto-stepping to $3/$15 on Aug 31 — off the model’s own reported tokens, so nothing goes untracked. Cheaper per token than Opus, though its tokenizer runs a bit heavier, so we show you the real number, not the sticker.
Included up to 50% of your weekly limit through ~July 19 (extended from July 7 → July 12 → July 19), then usage credits at $10/$50. WTClaude reads its billing-grade cost in your terminal and forecasts what your pace would cost in credits after the allowance — a labeled estimate, with a countdown to the cliff.
wtclaude compare-models
re-prices your recorded usage across Opus 4.8, Sonnet 5, and Fable 5 — what would this
month cost on each? Split by surface (Code billing-grade, Cowork a labeled estimate, Chat
excluded). In the CLI, the dashboard, and the companion.
Comparisons re-price your recorded usage, not the same task run on each model — every projection is a labeled estimate. We surface the cost of the choice; we don’t judge which model is “better.”
npx wtclaude setup
then
wtclaude compare-models.
Everything the CLI tracks, in a dashboard you can actually look at. Your real Claude Code cost over time, a session timeline that shows where the expensive turns were, the compare view, the “what-if” plan calculator, your overall plan limit gauge with reset countdowns, and your Agent-pool forecast tile estimate .
Cost figures are billing-grade for Claude Code run in your terminal. The forecast tile is a clearly-labeled estimate.
Open your dashboard →Work on a laptop and a desktop? Turn on opt-in cloud sync and WTClaude totals your real usage across all of them — the number no single-machine tracker can give you. (Local-first by default; nothing leaves your machine until you switch sync on, and you see a preview of exactly what syncs before it does.)
wtclaude sync --enable Opt-in · privacy-first · preview before anything leaves your machine.
Anthropic announced an Agent-SDK billing split for June 15, then paused it before it took effect. Nothing has changed — WTClaude's dual-pool view is built and ready if a revised version returns.
Anthropic announced that agent and claude -p
usage would move to a separate dollar budget — then paused it on June 15 before it took
effect. If a revised split lands, WTClaude already tracks it per-pool, billing-grade, with no
reinstall.
A projected daily and monthly agent-pool spend versus your included credits. Install early — every day you track sharpens the projection.
The cost math is billing-grade; the pool split is a heuristic, so this is a forecast — never your exact future bill.
A one-line credits-enough check — ready the moment a split does land.
Install now to get yours →Every number is labeled. Billing-grade for Claude Code cost. Inferred where we have to infer. Estimate for forward-looking projections. We never dress an estimate up as exact. (Today WTClaude tracks Claude Code; Cowork, Chat, and a unified view are coming next.)
The tracker is free and MIT-licensed. What’s coming is Guardian — a paid intelligence layer (personalized recommendations, anomaly detection, spend forecasting, coaching) at $2.99/mo · $24.99/year (≈$2.08/mo — save 30%). Install the free tracker now and Guardian inherits your full history from day one.
The tracker, the dashboard, and sync are all free and open-source. Guardian (the paid intelligence layer, $2.99/mo · $24.99/year (≈$2.08/mo — save 30%)) is what’s next.
The accuracy story
Why Your Claude Code Cost Tracker Disagrees With Your Bill →Billing-grade accuracy, backup & multi-machine sync, a full dashboard, billing-change readiness — the most complete Claude Code tracker.
Explore all features →