Highlights
- Dedicated Codex source mode
- Daily, monthly, total, session, and model reporting
- Fits side-by-side with combined and wrapped views
Feature
Codex CLI stats
Track OpenAI Codex CLI usage locally with token, cost, session, model, and date-based reports.
Intent
Feature
Focus
Codex CLI stats in vibestats is designed for people using the codex cli who want a dedicated usage tracker and not just a combined dashboard.
Next step
Relevant commands
npx vibestats codexnpx vibestats usage codex --totalnpx vibestats limits codexWhat codex cli stats means
Codex CLI stats is about getting a clear, local view of AI coding activity without building custom spreadsheets or one-off scripts.
Who this is for
People using the Codex CLI who want a dedicated usage tracker and not just a combined dashboard.
How vibestats handles it
vibestats reads Codex session history, keeps the reporting shape aligned with Claude-compatible usage, and exposes dedicated Codex views for totals, trends, and breakdowns.
What you get back
You can inspect Codex CLI usage in isolation, compare reporting windows, and keep a clean record of which models and sessions drove the most activity.
FAQ
Can vibestats help with codex cli stats?
Yes. vibestats is built to support codex cli 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
guides how-to-track-codex-cli-usageOpen the related vibestats page and continue the workflow from there.compare claude-code-vs-codex-cli-trackingOpen the related vibestats page and continue the workflow from there.features combined-ai-coding-statsOpen the related vibestats page and continue the workflow from there.