Tokemon, a free open-source Claude usage monitor, surfaced on Hacker News this week offering developers a local view of their token consumption without routing traffic through a third-party platform. The project — the name blends 'token' with the Pokémon franchise — targets developers using Claude Code or the Claude API who want cost visibility built into their workflow rather than buried in a web dashboard.
Install it via Homebrew (brew install --cask tokemon) and it reads your local Claude session log files directly from disk, polling every 30 seconds. The dashboard shows three things immediately: how much of your session limit you've consumed, your current burn rate in tokens per hour, and a projected time-to-limit at that pace. A per-project breakdown covers token spend by codebase across 7, 30, or 90-day windows — useful for anyone running multiple projects under one plan. Connecting an Anthropic Admin API key unlocks organisation-wide reporting: total spend, input/output token splits, cache hit rates, and a full usage history chart.
Alerting is configurable — webhooks fire at 50%, 70%, and 90% thresholds. A Raycast extension and a shell prompt integration via ~/.tokemon/statusline (with ANSI colour support for zsh/bash) cover developers who want usage data without leaving the terminal.
The project is MIT-licensed with no paid tier. It's one of several local-first monitoring tools that have appeared as Claude Code adoption has grown, alongside claude-code-usage-monitor and Usage4Claude. Unlike cloud observability platforms such as LangSmith or Helicone, Tokemon doesn't proxy or store your LLM traffic — it reads files already written to disk by the Claude client, and optionally queries the Admin API. No usage data leaves your machine unless you opt into that API connection.