Highlights
- Daily, monthly, total, session, and model views
- Token and estimated cost reporting
- Works with wrapped pages and activity heatmaps
Feature
Claude Code stats
Track Claude Code usage locally with daily, monthly, session, model, token, and cost reports.
Intent
Feature
Focus
Claude Code stats in vibestats is designed for developers who want a readable claude code usage tracker instead of raw local files.
Next step
Relevant commands
npx vibestatsnpx vibestats claudenpx vibestats --sessionsWhat claude code stats means
Claude Code stats is about getting a clear, local view of AI coding activity without building custom spreadsheets or one-off scripts.
Who this is for
Developers who want a readable Claude Code usage tracker instead of raw local files.
How vibestats handles it
vibestats reads Claude-compatible local usage artifacts, then turns them into daily tables, model breakdowns, totals, wrapped pages, and shareable aggregate outputs.
What you get back
You get a consistent answer to how much Claude Code you used, when usage spiked, which models dominated, and how token/cost patterns changed.
FAQ
Can vibestats help with claude code stats?
Yes. vibestats is built to support claude code stats with local reporting, aggregate pages, and command-line workflows.
Does this stay local?
Yes. vibestats is local-first. Prompts and responses stay out of the hosted pages unless you intentionally publish aggregate share output.
Where should I start?
Start with the command reference, then use the related links below to jump into wrapped reports, activity heatmaps, share pages, or diagnostics.
Related pages