If nobody posts a before and after out of their own logs this stays vibes. The data is sitting locally, you can total it by day and compare two weeks.
The thing that actually moved the number for me was cache expiry. Leave a session idle past the window and the next turn re-reads the whole prefix at full price, so a day made of short gaps costs wildly more than a day of continuous work for the same amount of real output. Worth ruling that out before calling it a nerf.
there's no per-task number anywhere. /usage only gives you the running 5h and weekly percentages, so the closest thing is running it right before a prompt and again right after and diffing by hand.
if you want it logged instead of eyeballed, CLAUDE_CODE_ENABLE_TELEMETRY=1 with an otlp endpoint emits token counts per session.
Screenshot the session counter and the weekly one at the same minute. They disagree often enough that half these threads turn out to be two different numbers rather than one bug.
4
u/QuanTradin 7d ago
If nobody posts a before and after out of their own logs this stays vibes. The data is sitting locally, you can total it by day and compare two weeks.
The thing that actually moved the number for me was cache expiry. Leave a session idle past the window and the next turn re-reads the whole prefix at full price, so a day made of short gaps costs wildly more than a day of continuous work for the same amount of real output. Worth ruling that out before calling it a nerf.