Highlights
- One combined scope across supported local sources
- Useful for retrospectives and weekly reporting
- Pairs well with activity and wrapped pages
Feature
Combined AI coding stats
Merge Claude-compatible and Codex CLI usage into one view for daily reporting, wrapped summaries, and activity analysis.
Intent
Feature
Focus
Combined AI coding stats in vibestats is designed for developers who switch between claude code and codex and want one reporting layer for both.
Next step
Relevant commands
npx vibestats allnpx vibestats --combinednpx vibestats --activity --combinedWhat combined ai coding stats means
Combined AI coding 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 switch between Claude Code and Codex and want one reporting layer for both.
How vibestats handles it
vibestats can aggregate supported local sources into a single combined scope, so you can compare trends across your entire AI coding workflow instead of splitting them by tool.
What you get back
You get one higher-level view of how often you coded with AI, how tokens and costs changed, and whether model mix or activity intensity shifted over time.
FAQ
Can vibestats help with combined ai coding stats?
Yes. vibestats is built to support combined ai coding 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
Continue by intent
compare single-source-vs-combined-trackingOpen the related vibestats page and continue the workflow from there.features ai-coding-wrappedOpen the related vibestats page and continue the workflow from there.features ai-coding-activity-heatmapOpen the related vibestats page and continue the workflow from there.