Javis603/token-monitor

EN | 简 | 繁 | KO | JA

One live dashboard for every AI coding tool, synced across every machine.

What is Token Monitor?

A desktop widget that shows live token usage and AI Tool Limits across 43+ 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.

Supported Tools

Token Monitor supports token usage, account-limit checks, and session details separately:

| Logo | Tool | Data path | Token Usage | AI Tool Limits | Session Details | |:---:|------|-----------|:---:|:---:|:---:| | | Claude Code | ~/.claude/projects/, ~/.claude/transcripts/ | ✅ | ✅ | ✅ | | | Codex | ~/.codex/ (sessions/, archived_sessions/) | ✅ | ✅ | ✅ | | | OpenCode | ~/.local/share/opencode/ (opencode*.db, storage/message/) | ✅ | ✅ | ✅ | | | Hermes Agent | ~/.hermes/state.db | ✅ | — | — | | | OpenClaw | ~/.openclaw/agents/ | ✅ | — | — | | | Cursor IDE / Cursor CLI / Grok Bot | ~/.config/tokscale/cursor-cache/ (account-level usage export) | ✅ | ✅ | — | | | Antigravity | ~/.gemini/ (antigravity/, antigravity-ide/, antigravity-backup/, antigravity-cli/conversations/) | ✅ | ✅ | — | | | Cline | VS Code globalStorage tasks (.../saoudrizwan.claude-dev/tasks/), ~/.cline/data/sessions/ | ✅ | ✅ | — | | | Amp | ~/.local/share/amp/threads/ | ✅ | — | — | | | Factory Droid | ~/.factory/sessions/ | ✅ | ✅ | — | | | Kimi CLI / Kimi Code / Kimi Work | ~/.kimi/sessions/, ~/.kimi-code/sessions/, /kimi-desktop/ | ✅ | ✅ | — | | | Qwen CLI | ~/.qwen/projects/ | ✅ | — | — | | | Grok Build | ~/.grok/ (sessions/, logs/unified.jsonl) | ✅ | ✅ | — | | | GitHub Copilot | VS Code workspaceStorage/*/chatSessions/, ~/.copilot/ (otel/, data.db, session-store.db) | ✅ | ✅ | — | | | Pi | ~/.pi/agent/sessions/ | ✅ | — | — | | | Oh My Pi | ~/.omp/agent/sessions/ | ✅ | — | — | | | Zed | ~/.local/share/zed/threads/threads.db | ✅ | ✅ | — | | | Kilo | ~/.local/share/kilo/kilo.db; VS Code globalStorage tasks (.../kilocode.kilo-code/tasks/) — extension logs on Linux & remote/WSL only | ✅ | — | — | | | Command Code | ~/.commandcode/projects/**/*.jsonl | ✅ | ✅ | — | | | MiMo Code / MiMo Desktop | ~/.local/share/mimocode/mimocode.db | ✅ | ✅ | — | | | Muse Code | ~/.local/share/muse/sessions/ | ✅ | — | — | | | ZCode / GLM | ~/.zcode/ (projects/, cli/db/db.sqlite) | ✅ | ✅ | — | | | Kiro | ~/.kiro/sessions/cli/, Kiro IDE globalStorage & kiro-cli DB | ✅ | ✅ | — | | | CodeBuddy | ~/.codebuddy/projects/ + IDE / VS Code extension logs | ✅ | — | — | | | WorkBuddy | ~/.workbuddy/projects/, ~/.workbuddy/workbuddy.db | ✅ | ✅ | — | | | Proma | ~/.proma/agent-sessions/*.jsonl | ✅ | — | — | | | Qoder | ~/.qoder-cn/projects/**/*.jsonl, legacy /QoderCN/SharedClientCache/cache/db/local.db (CN only) | ✅ | ✅ | — | | | Reasonix | ~/.reasonix/ (stats/, sessions/, projects/*/sessions/) | ✅ | — | — | | | DeepSeek / DeepSeek Harness | ~/.dsh/sessions/ (session.jsonl, session.jsonl.zstd) | ✅ | ✅ | ✅ | | | Cherry Studio | /CherryStudio/ (Data/Agents/.claude/projects/ V2, .claude/projects/ legacy) | ✅ | — | — | | | LM Studio | ~/.lmstudio/server-logs/**/*.log | ✅ | — | — | | | Unsloth Studio | ~/.unsloth/studio/studio.db | ✅ | — | — | | | Devin CLI / Devin Desktop | ~/.local/share/devin/cli/sessions.db, /Devin/User/acp-events/ | ✅ | ✅ | — | | | fx | ~/.fx/sessions/ | ✅ | — | — | | | TypeSafe | TypeSafe Console Cookie (billing balance and estimated token spend via usage data) | — | ✅ | — | | | OpenRouter | OpenRouter API key (usage/key limit; balance when credits access is authorized, documented for Management keys) | — | ✅ | — | | | Minimax | Minimax API key (Token Plan quota via Minimax API) | — | ✅ | — | | | Volcengine | Ark API key or Volcengine AK/SK (Ark Coding Plan & Agent Plan quota via Volcengine API) | — | ✅ | — | | | Ollama | Ollama Cloud cookie (session/weekly usage via ollama.com/settings) | — | ✅ | — | | | Trae CN | Trae CN access token (Trae CN / SOLO credits via trae.cn) | — | ✅ | — | | | Alibaba Cloud | Alibaba Cloud console cookie (Bailian / Model Studio Token Plan quota, Team & Personal) | — | ✅ | — | | | StepFun | StepFun Oasis-Token (Coding Plan / Token Plan quota) | — | ✅ | — | | | Third-party APIs | New API / Sub2API-compatible account presets (including compatible One API forks), a New API API-key preset, and a Custom balance endpoint | — | ✅ | — |

Notes, Custom balance endpoints, and data paths overridden by environment variables

• Paths above are the defaults. Token Monitor follows the same environment overrides Tokscale does — $XDG_DATA_HOME for the ~/.local/share/ roots, and per-tool variables such as $CODEX_HOME, $GROK_HOME, $HERMES_HOME, $KIMI_CODE_HOME, $UNSLOTH_STUDIO_HOME, $LM_STUDIO_HOME, $DSH_HOME, $REASONIX_STATE_HOME, $REASONIX_HOME and the $CLINE_* family.
• LM Studio tracking currently covers OpenAI-compatible /v1/chat/completions and /v1/responses requests recorded in server logs. Conversations started from LM Studio's built-in Chat UI and native /api/v1/chat requests are not included.
• Unsloth Studio tracks inference usage from studio.db: Studio chats and its local API. Local inference has zero API cost; recognized metered providers use Tokscale's price estimates. Training tokens are not included. See Unsloth source notes.
• Devin tracks Devin CLI sessions from the local sessions.db and Devin Desktop agent sessions from acp-events ACP logs; where both cover the same session the CLI database is authoritative. Desktop coverage depends on the connected ACP agent: only agents that write usage_update events locally are counted, and Devin Desktop's default devin-cloud agent meters its usage server-side, so a default Desktop setup reports no Desktop tokens. Session titles and project attribution come from the CLI database. See Devin source notes.
• Command Code transcripts do not contain actual token counts or per-message model metadata. Token usage is estimated from transcript text, while model attribution and derived cost may reflect the currently configured model rather than the model historically used for each request.
• The Cursor cache comes from Cursor's account-level usage export, so it covers usage from Cursor IDE, Cursor CLI, and Grok Bot. Token Monitor automatically detects accounts signed in through the Cursor desktop app and also supports adding accounts manually in Settings. The cache re-syncs automatically when stale, but newly finished sessions can take a few minutes to reach Cursor's dashboard, so usage updates on sync rather than instantly.
• Custom maps numeric JSON fields from one GET balance endpoint; OpenAI or Anthropic compatibility alone is not enough.

Qoder CN (local adapter)

Qoder CN token usage is read from the app's local data, not an API — enable it in Settings → tools (opt-in, off by default). Current builds persist Claude-compatible JSONL transcripts in the Qoder config directory's projects tree (normally ~/.qoder-cn/projects), while older builds wrote a SQLite database. The adapter reads both. The transcript path follows TOKEN_MONITOR_QODER_CN_PROJECTS_PATH, then QODERCN_CONFIG_DIR/projects, then the default; the legacy database is auto-detected per platform and can be overridden with TOKEN_MONITOR_QODER_CN_DB_PATH. See Qoder source notes.

This is an advanced local integration: the JSONL path needs no extra runtime, but reading the legacy database needs a sqlite3 CLI on PATH or a Node runtime with unflagged node:sqlite (Node ≥ 22.15; the Electron widget may need the CLI). Read failures retain the last complete snapshot. Only JSONL rows with reported token counts are included: current first-party plan-billed rows may expose credits and context occupancy but no reliable per-session context window, so their tokens cannot be reconstructed safely and are omitted from token totals. Their credits remain available in AI Tool Limits; BYOK/custom-model rows with measured tokens are counted normally.

Showcase

Customizable dashboard — choose which modules show and their order	Multiple accounts side by side, one-click switch of the active Codex account	Click any tool to expand input / output and cache-hit detail
Open a single session to break each prompt into tokens and tools used	Every model's usage and cost, aggregated across tools	Each device's usage, cost, and sync status — expand for per-machine detail

A year of activity heatmap and streaks, aggregated across all devices

A year of daily trends, stacked by tool / model, with K-line

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.

Features

Tracking usage

• Live token tracking — Claude Code, Codex, Cursor, GitHub Copilot, Antigravity, OpenCode, and 34+ 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, TWD, HKD, or CNY; 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 a running WSL distro is detected automatically and 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 28+ 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 — Claude, OpenAI, Cursor, and DeepSeek 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
• iOS widget support — Widgy and Scriptable through the Worker hub
• Privacy-first — prompts, responses, source code, and file contents stay on your machine

Interface & surfaces

• Breakdown views — grouped by tool, device, model, session, project, or account limits
• Menu bar (macOS) and system tray (Windows) popover — live cost, tokens, or the closest-to-empty provider limit % next to the icon
• Floating Bubble mode — collapses the widget into a draggable mini-window with click or hover preview and tray-style content
• Edge Dock (macOS & Windows) — keeps quotas and usage at the screen edge, with auto-hide, always-visible, or fullscreen auto-hide modes. Hover cards show account limits, recent sessions, and token usage. Choose, reorder, and configure items in Settings, and toggle it from the menu bar or system tray
• Menu bar layout composer — the menu bar and the floating bubble can use a built-in preset or a layout you build yourself: pick "Custom…" to add AI tool icons, quota bars, percentages, reset times, cost, the live token rate, or custom text, drag to reorder against a live preview, and give each item its own AI tool, account, quota window, and typeface
• Appearance controls — interface theme switching (incl. a light mode), per-tool vendor colours, glass opacity, blur, transparent window mode, and custom fonts
• Native macOS Widgets — View token usage and cost, trends, AI tool quota remaining and reset times, activity heatmaps, and breakdowns by tool or model in Small, Medium, and Large layouts on macOS 14+
• Customizable tool list — hide, pin, and reorder tools in the main dashboard without changing what gets tracked
• Recordable global shortcut — show or hide the window from anywhere
• Discord Rich Presence — broadcast today's tokens, cost, and top client (opt-in)

Installation

On macOS, install through the official Homebrew Cask:

brew install --cask token-monitor

Or download from GitHub Releases.

• macOS (Apple Silicon) — .dmg, signed and notarized
• macOS (Intel) — x64 .dmg, signed and notarized
• Windows 10/11 — setup and portable .exe, code-signed
• Linux x64 — .AppImage

Packaged builds check GitHub Releases automatically. When an update is available, the app shows an update indicator; supported platforms can also install from Settings → General.

First run

Local mode is the default: launch the app and it starts tracking this device. No hub, agent, or config required.

Multi-device sync

Pick ONE multi-device sync backend for your devices (and any headless agents). On each device, open the widget and pick a mode under Settings → Multi-device Sync. The widget contributes this device's usage automatically; run npm run agent only on machines without a widget. iCloud Drive is a macOS-widget-only option and does not support headless agents.

Option A — Host the hub from the widget (easiest, no CLI)

In the widget on one always-on machine, open Settings → Multi-device Sync and pick Host hub on this device. The widget generates a random secret and lists the LAN URLs other devices can connect to (Tailscale or ZeroTier addresses appear here too). On every other device, pick Connect to a hub and paste the URL + secret.

The hub runs while Token Monitor is running — quitting (not just closing the window) stops it for all connected devices.

Option B — Self-hosted Node hub (always-on headless machine)

# on the always-on machine
cp .env.example .env
set TOKEN_MONITOR_SECRET to something private, then:
npm run hub

Option C — Cloudflare Worker hub (across networks, including iPhone)

One-click deploy — Cloudflare will prompt for the TOKEN_MONITOR_SECRET during setup. Or deploy manually:

cd worker
npm install
npx wrangler login
npx wrangler secret put TOKEN_MONITOR_SECRET
npx wrangler deploy

Paste the deployed URL into each device's widget at Settings → Multi-device Sync. See worker/README.md for the iOS widget recipe and endpoint reference, or docs/API.md for the hub HTTP API.

Option D — iCloud Drive (macOS, no Hub server)

On each Mac signed into the same Apple ID, choose iCloud Drive in Settings → Multi-device Sync. This is an opt-in macOS-only path: Token Monitor writes one atomic snapshot per device and one subscription snapshot per writer under iCloud Drive/Token Monitor/sync-v1/, then each Mac aggregates the valid files locally. It uses no Token Monitor server, CloudKit, or credentials; provider API keys, cookies, and tokens stay local. iCloud Drive is eventually consistent, so another Mac may take a moment to appear or update, and a missing or malformed file never clears the last-good aggregate.

App data

App state lives in the OS user-data dir — delete it along with the app to fully uninstall.

| Platform | Path | |---