Token Tracker

Token Tracker

Keep track of token usage of your CLI agents while coding (claude and codex only).

Dashboard

Status bar + sidebar/editor views:



• Status bar meter: rolling 24-hour burn tokens vs tokenTracker.dailyTokenLimit
  (burn = input_tokens + output_tokens; cached tokens are not included in this total)
• Sidebar + editor dashboard:
  • 7-day chart, weekly comparison, per-provider table, live event feed
  • By project (24h): usage grouped by working directory when the tool reports it; comparative input vs output bar per project (cached is not part of the bar split)
• Source bars (Claude / Codex): rolling last 5 hours of burn vs your per-source caps (tokenTracker.dailyTokenLimitClaude / tokenTracker.dailyTokenLimitCodex)
• Rate-limit section:
  • Codex: authoritative windows when rollout rate_limits metadata is present
  • Claude (and Codex fallback): observed windows (5h / 7d) derived from local events; observed token counts use input + output only
• Local ingest API: POST to http://127.0.0.1:58417/ingest
• No backend, no account: data stays on-device in extension storage

Token accounting (how numbers are calculated)

• Each stored event has input_tokens, output_tokens, and optionally cached_tokens (e.g. Anthropic cache read/creation).
• total_tokens in the event store is always input_tokens + output_tokens — cached usage is not added into that total.
• Cost (when not supplied) can still use cached tokens for pricing estimates, but UI “burn” meters and source bars intentionally use input + output so cache traffic does not inflate the headline numbers.
• Claude Code: cache fields from local JSONL are stored as cached_tokens for cost/context; burn totals follo