Javis603/token-monitor

▲ 786 stars today★ 2,164⑂ 211

Local-first desktop widget for tracking token usage, costs, and limits across 37+ AI coding tools—including Claude Code, Codex, Cursor, OpenCode, and OpenClaw—with multi-device sync.

About Javis603/token-monitor

Javis603/token-monitor is an open-source project on GitHub, mainly written in JavaScript. Local-first desktop widget for tracking token usage, costs, and limits across 37+ AI coding tools—including Claude Code, Codex, Cursor, OpenCode It currently holds 2,164 stars and 211 forks with 0 open issues, and was last pushed on an unknown date (repository created unknown).

Project Overview

AI Homed tracks it on the Today's Trending board.

GitHub Repository Details

Repository Javis603/token-monitor · default branch - · size 0 KB · watchers 0 · source: GitHub REST API and repository README

README

EN | | | KO | JA

https://github.com/Javis603/token-monitor/blob/HEAD/Token Monitor logo

Token Monitor

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

https://github.com/Javis603/token-monitor/blob/HEAD/Latest release https://github.com/Javis603/token-monitor/blob/HEAD/Total downloads https://github.com/Javis603/token-monitor/blob/HEAD/Windows 10 or later https://github.com/Javis603/token-monitor/blob/HEAD/macOS 12 or later https://github.com/Javis603/token-monitor/blob/HEAD/Linux x64 https://github.com/Javis603/token-monitor/blob/HEAD/Discord https://github.com/Javis603/token-monitor/blob/HEAD/License: MIT

What is Token Monitor?

A desktop widget that shows live token usage and AI Tool Limits across 37+ 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 | |:---:|------|-----------|:---:|:---:|:---:| | https://github.com/Javis603/token-monitor/blob/HEAD/Claude Code | Claude Code | ~/.claude/projects/, ~/.claude/transcripts/ | ✅ | ✅ | ✅ | | https://github.com/Javis603/token-monitor/blob/HEAD/Codex | Codex | ~/.codex/ (sessions/, archived_sessions/) | ✅ | ✅ | ✅ | | https://github.com/Javis603/token-monitor/blob/HEAD/OpenCode | OpenCode | ~/.local/share/opencode/ (opencode*.db, storage/message/) | ✅ | ✅ | ✅ | | https://github.com/Javis603/token-monitor/blob/HEAD/Hermes Agent | Hermes Agent | ~/.hermes/state.db | ✅ | — | — | | https://github.com/Javis603/token-monitor/blob/HEAD/OpenClaw | OpenClaw | ~/.openclaw/agents/ | ✅ | — | — | | https://github.com/Javis603/token-monitor/blob/HEAD/Cursor | Cursor IDE / Cursor CLI | ~/.config/tokscale/cursor-cache/ (account-level usage export) | ✅ | ✅ | — | | https://github.com/Javis603/token-monitor/blob/HEAD/Antigravity | Antigravity | ~/.gemini/ (antigravity/, antigravity-ide/, antigravity-backup/, antigravity-cli/conversations/) | ✅ | ✅ | — | | https://github.com/Javis603/token-monitor/blob/HEAD/Cline | Cline | VS Code globalStorage tasks (.../saoudrizwan.claude-dev/tasks/), ~/.cline/data/sessions/ | ✅ | — | — | | https://github.com/Javis603/token-monitor/blob/HEAD/Amp | Amp | ~/.local/share/amp/threads/ | ✅ | — | — | | https://github.com/Javis603/token-monitor/blob/HEAD/Factory Droid | Factory Droid | ~/.factory/sessions/ | ✅ | ✅ | — | | https://github.com/Javis603/token-monitor/blob/HEAD/Kimi | Kimi CLI / Kimi Code / Kimi Work | ~/.kimi/sessions/, ~/.kimi-code/sessions/, /kimi-desktop/ | ✅ | ✅ | — | | https://github.com/Javis603/token-monitor/blob/HEAD/Qwen | Qwen CLI | ~/.qwen/projects/ | ✅ | — | — | | https://github.com/Javis603/token-monitor/blob/HEAD/Grok Build | Grok Build | ~/.grok/ (sessions/, logs/unified.jsonl) | ✅ | ✅ | — | | https://github.com/Javis603/token-monitor/blob/HEAD/GitHub Copilot | GitHub Copilot | VS Code workspaceStorage/*/chatSessions/, ~/.copilot/ (otel/, data.db) | ✅ | ✅ | — | | https://github.com/Javis603/token-monitor/blob/HEAD/Pi | Pi / Oh My Pi | ~/.pi/agent/sessions/, ~/.omp/agent/sessions/ | ✅ | — | — | | https://github.com/Javis603/token-monitor/blob/HEAD/Zed | Zed | ~/.local/share/zed/threads/threads.db | ✅ | ✅ | — | | https://github.com/Javis603/token-monitor/blob/HEAD/Kilo | Kilo | ~/.local/share/kilo/kilo.db; VS Code globalStorage tasks (.../kilocode.kilo-code/tasks/) — extension logs on Linux & remote/WSL only | ✅ | — | — | | https://github.com/Javis603/token-monitor/blob/HEAD/Command Code | Command Code | ~/.commandcode/projects/**/*.jsonl | ✅ | ✅ | — | | https://github.com/Javis603/token-monitor/blob/HEAD/MiMo Code | MiMo Code | ~/.local/share/mimocode/mimocode.db | ✅ | ✅ | — | | https://github.com/Javis603/token-monitor/blob/HEAD/ZCode | ZCode / GLM | ~/.zcode/ (projects/, cli/db/db.sqlite) | ✅ | ✅ | — | | https://github.com/Javis603/token-monitor/blob/HEAD/Kiro | Kiro | ~/.kiro/sessions/cli/, Kiro IDE globalStorage & kiro-cli DB | ✅ | ✅ | — | | https://github.com/Javis603/token-monitor/blob/HEAD/CodeBuddy | CodeBuddy | ~/.codebuddy/projects/ + IDE / VS Code extension logs | ✅ | — | — | | https://github.com/Javis603/token-monitor/blob/HEAD/WorkBuddy | WorkBuddy | ~/.workbuddy/projects/, ~/.workbuddy/workbuddy.db | ✅ | ✅ | — | | https://github.com/Javis603/token-monitor/blob/HEAD/Proma | Proma | ~/.proma/agent-sessions/*.jsonl | ✅ | — | — | | https://github.com/Javis603/token-monitor/blob/HEAD/Qoder | Qoder | /QoderCN/SharedClientCache/cache/db/local.db (CN only) | ✅ | ✅ | — | | https://github.com/Javis603/token-monitor/blob/HEAD/Reasonix | Reasonix | ~/.reasonix/ (stats/, sessions/, projects/*/sessions/) | ✅ | — | — | | https://github.com/Javis603/token-monitor/blob/HEAD/DeepSeek | DeepSeek / DeepSeek Harness | ~/.dsh/sessions/ (session.jsonl, session.jsonl.zstd) | ✅ | ✅ | ✅ | | https://github.com/Javis603/token-monitor/blob/HEAD/Cherry Studio | Cherry Studio | /CherryStudio/ (Data/Agents/.claude/projects/ V2, .claude/projects/ legacy) | ✅ | — | — | | https://github.com/Javis603/token-monitor/blob/HEAD/LM Studio | LM Studio | ~/.lmstudio/server-logs/**/*.log | ✅ | — | — | | https://github.com/Javis603/token-monitor/blob/HEAD/Unsloth | Unsloth Studio | ~/.unsloth/studio/studio.db | ✅ | — | — | | https://github.com/Javis603/token-monitor/blob/HEAD/OpenRouter | OpenRouter | OpenRouter API key (usage/key limit; balance when credits access is authorized, documented for Management keys) | — | ✅ | — | | https://github.com/Javis603/token-monitor/blob/HEAD/Minimax | Minimax | Minimax API key (Token Plan quota via Minimax API) | — | ✅ | — | | https://github.com/Javis603/token-monitor/blob/HEAD/Volcengine | Volcengine | Ark API key or Volcengine AK/SK (Ark Coding Plan & Agent Plan quota via Volcengine API) | — | ✅ | — | | https://github.com/Javis603/token-monitor/blob/HEAD/Ollama | Ollama | Ollama Cloud cookie (session/weekly usage via ollama.com/settings) | — | ✅ | — | | https://github.com/Javis603/token-monitor/blob/HEAD/Trae CN | Trae CN | Trae CN access token (Trae CN / SOLO credits via trae.cn) | — | ✅ | — | | https://github.com/Javis603/token-monitor/blob/HEAD/Alibaba Cloud | Alibaba Cloud | Alibaba Cloud console cookie (Bailian / Model Studio Token Plan quota, Team & Personal) | — | ✅ | — | | https://github.com/Javis603/token-monitor/blob/HEAD/Third-party APIs | 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.
  • 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 Cursor IDE and Cursor CLI alike. 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 SQLite database, not an API — enable it in Settings → tools (opt-in, off by default). The database is auto-detected per platform: macOS ~/Library/Application Support/QoderCN/SharedClientCache/cache/db/local.db, Windows %APPDATA%\QoderCN\SharedClientCache\cache\db\local.db, Linux ~/.config/QoderCN/SharedClientCache/cache/db/local.db — overridable with TOKEN_MONITOR_QODER_CN_DB_PATH.

This is an advanced local integration: reading needs a sqlite3 CLI on PATH or a Node runtime with unflagged node:sqlite (Node ≥ 23.4; the Electron widget may need the CLI). Read failures are logged, and an existing complete snapshot is retained instead of being replaced with zero usage. Costs are estimated from the models.dev catalog for each mapped model; the adapter may break if Qoder changes its database schema.

Showcase

https://github.com/Javis603/token-monitor/blob/HEAD/Home View
Customizable dashboard — choose which modules show and their order
https://github.com/Javis603/token-monitor/blob/HEAD/Limits View
Multiple accounts side by side, one-click switch of the active Codex account
https://github.com/Javis603/token-monitor/blob/HEAD/Tools View
Click any tool to expand input / output and cache-hit detail
https://github.com/Javis603/token-monitor/blob/HEAD/Session View
Open a single session to break each prompt into tokens and tools used
https://github.com/Javis603/token-monitor/blob/HEAD/Models View
Every model's usage and cost, aggregated across tools
https://github.com/Javis603/token-monitor/blob/HEAD/Devices View
Each device's usage, cost, and sync status — expand for per-machine detail
https://github.com/Javis603/token-monitor/blob/HEAD/Usage Dashboard Overview
A year of activity heatmap and streaks, aggregated across all devices
https://github.com/Javis603/token-monitor/blob/HEAD/Usage Dashboard Trends
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

Limits, trends & export

Multi-device & deployment

Interface & surfaces

Installation

On macOS, install through the official Homebrew Cask:

brew install --cask token-monitor

Or download from GitHub Releases.

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 hub backend that all your devices (and any headless agents) connect to. 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.

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)

Deploy to Cloudflare

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.

App data

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

| Platform | Path | |----------|------| | macOS | ~/Library/Application Support/Token Monitor/ | | Windows | %APPDATA%/Token Monitor/ | | Linux | ~/.config/Token Monitor/ |

Build from source

To build your own installer, use Node.js 22.15+ on the target OS (electron-builder can't cross-build a macOS .dmg on Windows, or vice-versa).

npm install
npm run dist:mac     # macOS arm64 .dmg           → dist/
npm run dist:mac:x64 # macOS Intel x64 .dmg       → dist/
npm run dist:win     # Windows x64 installer .exe → dist/
npm run dist:linux   # Linux x64 AppImage         → dist/
npm run pack         # unpacked app dir (no installer), for quick local testing

Output lands in dist/. Windows and Linux use the matching dist:* script above on the target OS. Packaging the macOS release build requires a local Developer ID Application signing identity; use npm start for local development or unsupported platforms.

Runtime and packaging scripts explicitly ensure the pinned tokscale binary on the four vendored targets. Other source platforms keep the npm binary and filter clients it does not support; npm install, lint, and tests do not download it.

How it works

Mode A — Local (default, no setup)
    widget (Electron) ──▶ tokscale ──▶ ~/.claude, ~/.codex, $HERMES_HOME

Mode B — Sync (opt-in, multi-device) device A agent ──▶ device B agent ──▶ hub ──▶ widget on any device device C agent ──▶

The widget chooses local vs sync mode based on Settings → Multi-device Sync. The hub itself can run as a separate npm run hub process, a Cloudflare Worker, or directly inside one of the widgets (Host mode). In sync mode the hub pushes aggregated stats to every connected widget over Server-Sent Events, so updates on one device appear on the others within a few seconds.

Session data retention

With Preserve deleted session usage enabled (Settings → Collection), Token Monitor archives observed daily tool/model usage locally with no time limit — so even after a source tool prunes its own sessions, the heatmap and trends are unaffected.

Advanced: extend the source tool's own retention


The heatmap and sync payload use a rolling 370-day window (older observations remain available locally for future views). Claude Code keeps only 30 days of transcripts by default (cleanupPeriodDays); to keep the full rolling year before the archive kicks in, raise it in ~/.claude/settings.json before the window passes:

{
  "cleanupPeriodDays": 370
}

A larger value keeps more, at the cost of transcripts living on disk for as long as you set. tokscale's Session Data Retention table covers the other tools' defaults and config paths.

This archive only covers days Token Monitor has already observed; data deleted before it started tracking cannot be recovered.

Settings

There are two places to configure Token Monitor; day-to-day use only needs the first:

GitHub Stars & Activity

2,164Stars
211Forks
0Open issues
JavaScriptLanguage

GitHub Popularity

GitHub stars2,164
Forks211
Open issues0
Primary languageJavaScript
License-
Stars gained today786
Created-
Last pushed-

Trending History

Monthly boardrank #55 · ▲ 786 stars

Related AI Projects

1

addyosmani / agent-skills

JavaScript★ 94,981⑂ 10,074▲ 307 stars
2

asgeirtj / system_prompts_leaks

JavaScript★ 67,264⑂ 10,918▲ 579 stars
3

tt-a1i / archify

JavaScript★ 63,980⑂ 4,243▲ 1,373 stars
4

cloudflare / security-audit-skill

JavaScript★ 5,267⑂ 320▲ 1,434 stars
5

darkzOGx / youtube-automation-agent

JavaScript★ 3,551⑂ 1,015▲ 56 stars
6

xuanyustudio / LocalMiniDrama

JavaScript★ 1,746⑂ 422▲ 29 stars
7

plugin87 / ux-ui-agent-skills

JavaScript★ 1,466⑂ 140▲ 93 stars
8

atlassian / atlassian-mcp-server

JavaScript★ 1,111⑂ 129▲ 5 stars

More AI Rankings