Highlights
- Input, output, cache read, and cache write visibility
- Estimated cost alongside usage volume
- Works across source-specific and combined views
Feature
Token and cost tracking
Track input, output, cache, total token volume, and estimated cost across AI coding sessions.
Intent
Feature
Focus
Token and cost tracking in vibestats is designed for developers who need a usable token and cost tracker for ai coding workflows.
Next step
Relevant commands
npx vibestats --totalnpx vibestats --last 7npx vibestats usage all --dailyWhat token and cost tracking means
Token and cost tracking 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 need a usable token and cost tracker for AI coding workflows.
How vibestats handles it
vibestats keeps token categories visible, estimates cost from the aggregated usage, and lets you compare totals across time windows, sources, and report shapes.
What you get back
You can understand usage spikes in budget terms, separate token volume from price signals, and build a better mental model for AI coding spend.
FAQ
Can vibestats help with token and cost tracking?
Yes. vibestats is built to support token and cost tracking 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
Continue by intent
guides how-to-measure-ai-token-costsOpen the related vibestats page and continue the workflow from there.compare token-volume-vs-cost-estimationOpen the related vibestats page and continue the workflow from there.features model-breakdownOpen the related vibestats page and continue the workflow from there.