Usage explained · 5 min
Why your Claude Code token counts look different
Raw tokens, cache reads, and weighted tokens answer different questions. Here is how to compare them without confusing usage with a bill.
Read guideClaude Code clears its local logs after about 30 days. claudeusage keeps a history of your token counts, estimated API cost and active hours through an open-source CLI. Never your chats: no prompts, no code, nothing else leaves your machine.
npx claudeusage-syncFree, open-source CLI · Node.js 22+
Community activity
Across the board
All time
$324,282.87
149
55.2B
55,186,868,985
15.1Kh
15,122 hours
Cost is estimated at public API rates, not subscription bills.
Public board
page 1 of 6
Estimated API cost, not subscription bills. How we count usage
From your terminal to your profile
The CLI reads local usage records and uploads numeric summaries. You can inspect the payload before sending it. Read the setup guide
Use npx claudeusage-sync. Add --dry-run to preview the aggregate payload before uploading.
Sign in with Google or GitHub and choose a public name. Staying anonymous is an option.
Review your totals and model mix. Run the command again whenever you want to upload new activity.
Field notes
Usage explained · 5 min
Raw tokens, cache reads, and weighted tokens answer different questions. Here is how to compare them without confusing usage with a bill.
Read guideCost explained · 4 min
A profile can show thousands of dollars in estimated usage without you owing that amount. Here is what the cost number actually means.
Read guideSetup guide · 4 min
Install nothing globally. Preview your local usage, approve a device, and keep one profile for the machines you work on.
Read guide