Highlights
- Machine-readable JSON output
- Fits shell scripts and downstream systems
- Useful for custom dashboards and weekly reports
Feature
JSON and automation exports
Generate machine-readable vibestats output for dashboards, automations, scripts, and downstream analytics.
Intent
Feature
Focus
JSON and automation exports in vibestats is designed for developers who want to feed vibestats output into scripts, agents, dashboards, or reporting pipelines.
Next step
Relevant commands
npx vibestats --jsonnpx vibestats --claude-limits --jsonnpx vibestats usage codex --total --jsonWhat json and automation exports means
JSON and automation exports 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 to feed vibestats output into scripts, agents, dashboards, or reporting pipelines.
How vibestats handles it
vibestats supports JSON output and predictable command surfaces so you can build automations around usage totals, date windows, model grouping, and share publishing.
What you get back
You can keep the human-readable CLI output for fast checks and still pipe structured data into your own tooling when you need more control.
FAQ
Can vibestats help with json and automation exports?
Yes. vibestats is built to support json and automation exports 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 terminal-table-vs-json-outputOpen the related vibestats page and continue the workflow from there.use-cases engineering-managersOpen the related vibestats page and continue the workflow from there.guides how-to-compare-model-usageOpen the related vibestats page and continue the workflow from there.