Guide library

AI coding analytics guides

Read practical guides for tracking Claude Code usage, tracking Codex CLI usage, creating wrapped reports, building activity heatmaps, and sharing aggregate stats.

8 pagesBuilt around real vibestats workflows instead of generic SEO filler.
Internal linksEach page connects to related features, guides, and use cases.
Search intentEvery page is focused on one product or reporting question.

Guide

How to track Claude Code usage

A practical guide to tracking Claude Code usage locally with vibestats.

  • Start with daily usage, then refine
  • Model and session views answer different follow-up questions
  • Diagnostics help when the totals look confusing

Guide

How to track Codex CLI usage

A practical guide to tracking OpenAI Codex CLI usage locally with vibestats.

  • Codex works best as its own first view
  • Total and session views answer different questions
  • Combined reporting is a second step, not the first

Guide

How to create an AI coding wrapped

A practical guide to generating a wrapped-style AI coding recap with vibestats.

  • Wrapped is the best narrative recap view
  • Quiet mode is useful for share-first workflows
  • Heatmaps complement wrapped, not replace it

Guide

How to build an AI activity heatmap

A practical guide to generating a GitHub-style AI coding activity heatmap with vibestats.

  • Heatmaps are best for rhythm and consistency
  • Metric choice changes the story
  • Hosted pages are easier to reuse in updates

Guide

How to measure AI token costs

A practical guide to measuring token volume and estimated cost in vibestats.

  • Totals are the cleanest starting point
  • Tokens and cost are related but not identical
  • Model views help explain cost shifts

Guide

How to share AI coding stats

A practical guide to turning local vibestats output into shareable aggregate pages.

  • 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 read Claude diagnostics

A practical guide to using vibestats Claude diagnostics commands for local state and limit clues.

  • Diagnostics complement usage reports
  • Best used when something looks off
  • Local file visibility beats guesswork

Guide

How to compare model usage

A practical guide to comparing AI model usage in vibestats across reporting windows and source scopes.

  • Stable windows matter more than perfect totals
  • Model share is easier to read when grouped directly
  • Source context helps interpret model shifts