Highlights
- Per-session reporting
- Useful for debugging spikes and outliers
- Supports main-session vs subagent-aware workflows
Feature
Session breakdown
Inspect AI coding usage per session so you can separate heavy sessions from routine daily activity.
Intent
Feature
Focus
Session breakdown in vibestats is designed for people who need to analyze work session by session instead of only looking at daily totals.
Next step
Relevant commands
npx vibestats --sessionsnpx vibestats --last 7 --sessionsnpx vibestats codex --sessionsWhat session breakdown means
Session breakdown is about getting a clear, local view of AI coding activity without building custom spreadsheets or one-off scripts.
Who this is for
People who need to analyze work session by session instead of only looking at daily totals.
How vibestats handles it
vibestats can group usage by session, helping you see where long runs, subagent-heavy flows, or bursty work sessions changed the overall totals.
What you get back
You can spot outlier sessions, distinguish main sessions from subagent activity, and keep debugging or reporting closer to actual working sessions.
FAQ
Can vibestats help with session breakdown?
Yes. vibestats is built to support session breakdown 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
compare session-breakdown-vs-model-breakdownOpen the related vibestats page and continue the workflow from there.features claude-diagnosticsOpen the related vibestats page and continue the workflow from there.features token-and-cost-trackingOpen the related vibestats page and continue the workflow from there.