Highlights
- Share the surface that fits the audience
- Aggregate pages are better than screenshots
- Stored share pages are better than legacy payload URLs
Guide
How to share AI coding stats
A practical guide to turning local vibestats output into shareable aggregate pages.
Intent
Guide
Focus
How to share AI coding stats is a practical workflow page for turning local AI coding usage into something readable and repeatable.
Next step
Relevant commands
npx vibestats --sharenpx vibestats --wrapped --quietnpx vibestats --activity --share --days 365Step 1
Generate the report you want to share
Start with a usage report, wrapped page, or activity heatmap depending on the audience.
Step 2
Publish an aggregate share page
Use the share-aware command flow so the result becomes a hosted page rather than a terminal-only artifact.
Step 3
Keep the page at the stats layer
Share the aggregate result, not the raw local context that produced it.
Why this guide exists
Most AI coding reporting problems are not about one missing command. They are about choosing the right surface: daily usage, wrapped summaries, activity heatmaps, cost views, or shareable aggregate pages.
What to expect
This guide stays focused on vibestats workflows and the pages already documented in the public command reference, so you can move from local data to a readable result quickly.
FAQ
What is the fastest way to approach how to share ai coding stats?
Start with the relevant command, verify the output locally, then decide whether you need a share page, a wrapped summary, or a heatmap for communication.
Do I need to upload raw conversations for these guides?
No. vibestats works from local usage artifacts and only turns aggregate results into hosted pages when you explicitly publish them.
Related pages
Continue by intent
features share-pagesOpen the related vibestats page and continue the workflow from there.compare querystring-shares-vs-stored-share-pagesOpen the related vibestats page and continue the workflow from there.features privacy-first-analyticsOpen the related vibestats page and continue the workflow from there.