Skip to content
| Marketplace
Sign in
Visual Studio Code>Visualization>VibalyticsNew to Visual Studio Code? Get it now.
Vibalytics

Vibalytics

bigyap

| (0) | Free
Local activity stats for Claude Code and Codex CLI usage in VS Code — tokens, sessions, and messages, parsed entirely from your own machine.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Vibalytics

Local activity stats for Claude Code and Codex CLI usage, right inside VS Code — tokens, sessions, messages, cost estimates, and per-model breakdowns, all parsed entirely from your own machine.

Why

If you live in Claude Code or Codex, you have no easy way to see how much you're actually using them. Vibalytics reads the session logs those tools already write to disk and turns them into a dashboard — no accounts, no API keys, nothing leaves your computer.

Features

  • Status bar metric — a live glance at today's tokens (or sessions/messages) for Claude and Codex, configurable.
  • Sidebar dashboard — a compact activity view in the VS Code activity bar: recent activity, last-week chart, a 10-week heatmap, top models, recent sessions, and top projects.
  • Full dashboard panel — a wide, tabbed view (open via the status bar or the Expand button):
    • Overview — all-time / today / this-week / this-month totals, token composition (input · output · cache read · cache write), and rolling usage windows (last hour / 5 hours / 7 days).
    • Models — per-model token, request, and estimated-cost breakdown.
    • Projects — filterable, sortable table of usage by workspace.
    • Sessions — recent sessions with per-model filtering.
  • Cache hit rate surfaced inline, so you can see how much of your usage is served from prompt cache.
  • Cost estimates — a rough ~$ figure per model/project from a built-in pricing table (best-effort; see note below).

Privacy

Everything is computed locally by reading log files. Vibalytics does not use API keys, make network requests, or send your data anywhere.

It reads:

  • ~/.claude/projects — Claude Code session logs
  • ~/.codex/sessions (and ~/.codex/archived_sessions) — Codex CLI session logs

Settings

Setting Default Description
vibalytics.statusBar.metric tokens What the status bar shows: tokens, sessions, or messages.
vibalytics.statusBar.period today Time window for the status bar: today, week, or allTime.
vibalytics.refreshIntervalSeconds 30 How often to poll log files for changes.
vibalytics.claudeCode.logsPath (auto) Override the Claude Code logs directory.
vibalytics.codex.logsPath (auto) Override the Codex CLI logs directory.
vibalytics.codex.includeArchived true Include ~/.codex/archived_sessions in totals.

Commands

  • Vibalytics: Open Usage Dashboard
  • Vibalytics: Refresh Usage Stats
  • Vibalytics: Full Rescan (clear cache) — re-reads all logs from scratch (useful after upgrading).

Note on cost estimates

Costs are estimated from a built-in, hardcoded price table matched by model family. They are a rough guide, not a bill — published prices change over time, and any model not in the table shows no cost rather than a guess. Token and message counts are exact; dollar figures are approximate.


Enjoying Vibalytics? Support development on Patreon. 💜

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
© 2026 Microsoft