Highlights
- Local-first reporting model
- Aggregate shares instead of raw transcripts
- Fits privacy-sensitive development workflows
Feature
Privacy-first analytics
Use local-first AI coding analytics without sending prompts, responses, or project paths to a hosted dashboard.
Intent
Feature
Focus
Privacy-first analytics in vibestats is designed for developers and teams who need reporting but do not want raw coding conversations copied into a saas by default.
Next step
Relevant commands
npx vibestats --confignpx vibestats --quietnpx vibestats --jsonWhat privacy-first analytics means
Privacy-first analytics is about getting a clear, local view of AI coding activity without building custom spreadsheets or one-off scripts.
Who this is for
Developers and teams who need reporting but do not want raw coding conversations copied into a SaaS by default.
How vibestats handles it
vibestats keeps the default workflow local and only publishes aggregate share data when you explicitly ask for a page or artifact.
What you get back
You retain control over sensitive coding context while still getting readable reports for costs, trends, wrapped summaries, and activity views.
FAQ
Can vibestats help with privacy-first analytics?
Yes. vibestats is built to support privacy-first analytics 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