What is Token Monitor?
A desktop app that shows live token usage and AI Tool Limits across 54+ AI coding tools — Claude Code, Codex, Cursor, GitHub Copilot, Cherry Studio, and more — with real-time multi-device sync, historical usage trends, and breakdowns by tool, device, model, session, or project. It lives wherever you look: the main window, the MacBook notch, the menu bar or system tray, the edge of the screen, a floating bubble, and native macOS widgets.
Supported Tools
Token usage, AI Tool Limits and session details from the AI coding tools and providers you already use:
Showcase
On your desktop
Inside the app
Usage Dashboard
Why Token Monitor?
Most usage monitors are useful on the machine they run on. Token Monitor is built for multi-device work: each device watches its own local logs, sends summary updates to your hub, and every connected widget sees token changes almost immediately.
Quick Install
On macOS, install through the official Homebrew Cask:
brew install --cask token-monitor
Or download the app for macOS, Windows, or Linux from GitHub Releases.
Launch the app to start tracking this device locally, with no hub setup required. See Installation for full details.
Features
Tracking usage
- Live token tracking — Claude Code, Codex, Cursor, GitHub Copilot, Antigravity, OpenCode, and 42+ AI tools, with the UI updating within seconds of each turn (full list in the table above)
- Live token rate — an optional live readout of generation speed in
tok/s or total burn in tok/min
- Per-session detail — open a session to see tokens per prompt, expandable to each reply's exact token split and tools used (read on-demand from local transcripts or databases, never synced)
- Cache hit statistics — click any tool or model to expand a detailed breakdown of input tokens (cache hit vs miss), output tokens, and hit-rate percentages
- Cost & currency — cost alongside token counts, shown in USD, CNY, TWD, HKD, KRW, JPY, BRL and other supported currencies; exchange rates auto-update daily and can be manually overridden in Settings
- Custom scan paths — point a tool at extra session folders when yours live outside the defaults
- WSL usage (Windows) — file-based usage from running WSL distros is merged about every 5 minutes; SQLite-backed tools such as OpenCode and Hermes may require a headless agent inside WSL
Limits, trends & export
- AI Tool Limits detection — provider-specific session, daily, weekly, billing, and credits windows for Claude Code, Codex, Cursor, OpenRouter, third-party APIs, GLM, Kimi, and 34+ providers, including multiple OpenRouter/third-party profiles and balance-style accounts (Claude credits, DeepSeek prepaid balance and spend history, third-party balances)
- Multiple accounts & Codex switching — track several accounts per provider, each with its own limits; a tracked Codex account can be switched as the active local account in one click, without re-authenticating
- Codex reset forecast — an optional third-party forecast below Codex limits, showing the expected reset time, the reset type (Regular or Banked), and when the window last reset
- Preserve deleted session usage — many tools prune old sessions (Claude Code drops transcripts after 30 days by default), losing that history. When enabled, Token Monitor archives observed daily tool/model usage locally so the heatmap and trends survive even after the source files are gone (see Session data retention below)
- Usage Trends & Dashboard — a home-screen activity heatmap and trend chart, plus a dedicated dashboard window with streaks and stacked per-tool/per-model history (bar and K-line views) across all your devices
- Fixed usage ranges — switch between This week, Last 7 days, and Last 30 days alongside the native day, month, and total periods
- Optional Status view — official provider status pages, with manual or interval re-checks
- Data export — export usage as tool-agnostic CSV + JSON, manually or auto-written to a folder, for spreadsheets, Obsidian, Grafana, or scripts; see docs/export.md
- Subscription records — record by hand what each AI account actually costs; the plan label's tooltip then reports the price, the next renewal or end date, time subscribed, and the month's usage cost as a multiple of what the plan costs, for recurring plans and top-up ledgers alike
Multi-device & deployment
- Real-time multi-device sync — hub-backed sync uses Server-Sent Events to push updates to other devices within seconds; iCloud Drive sync is eventually consistent
- Local-first — no servers needed for single-device use
- Self-hosted sync backend — in-widget hub, Node CLI hub, or Cloudflare Worker
- Headless agent — reports usage from servers, SSH hosts, and WSL without the desktop app; see Headless agent
- iOS widget support — Widgy and Scriptable through the Worker hub
- Privacy-first — prompts, responses, source code, and file contents stay on your machine
This is the beginning of the README. Read the rest at the original. Read the full README ↗
