WhereMyTokens

Claude Code, Codex, and Antigravity token usage, live in your Windows tray.

한국어 · 日本語 · 中文 · Español

Download · First Run · Screenshots · macOS Edition

WhereMyTokens is a local-first desktop app for monitoring AI coding usage: quota windows, token totals, API-equivalent cost estimates, cache efficiency, sessions, model usage, activity patterns, and git output.

Built by a Korean developer who uses Claude Code daily, scratching my own itch.

Download

Looking for the menu bar version? See the separate WhereMyTokens for macOS repository, which has its own mac-vX.Y.Z release track and DMG/ZIP downloads.

By downloading or installing, you agree to the End-User License Agreement.

Japanese UI is built into the Windows app. It follows your system language by default on Japanese Windows, and you can override it from Settings → General → Language. Thanks to @restructure-git for the translation and key-structure groundwork in PR #37.

First Run

Chinese UI and Currency

Choose Simplified Chinese in Settings → General → Language. Simplified Chinese Windows is detected automatically; Traditional Chinese locales keep the English fallback. Help, tray menus, login notices, and usage alerts are included. Thanks to @lizi1997 for PR #61 and the additional translation patch in #60.

Settings → Currency supports USD, KRW, and CNY. Exchange rates are manual (CNY defaults to 7.2 per USD), not live market quotes. Currency changes affect display only, including the tray; stored USD usage is unchanged. This release also fixes Codex incorrectly appearing offline when account credits are present. No re-login or history reset is required for that fix.

1. Install with WhereMyTokens-Setup.exe, or extract the portable ZIP and run WhereMyTokens.exe.
2. Open the dashboard from the Windows tray.
3. Enable the providers you use: Claude Code, Codex, Antigravity, or any combination.
4. Enable Claude Code Integration to register the official statusLine bridge for live Claude quota data.

What's New

After upgrade, historical usage is checked locally. When legacy checkpoints need rebuilding, verification retries automatically after initial indexing completes. Only proven overcounts are corrected, with a local backup; unverified history remains unchanged. See Settings → Data for results and rechecking.

Full changelog

Highlights

• provider checkboxes for Claude Code, Codex, Antigravity, or any combination.
• Provider adapters live under src/main/providers/ and translate provider-reported limits into one canonical Quota Entry shape, separate from local token/cost usage.
• Dynamic Claude Code, Codex, and Antigravity quota cards preserve provider scope, reset time, known-or-unknown duration, and explicit unlimited state. Antigravity 2.x uses the provider-reported Gemini Models and Claude and GPT models shared groups, with legacy per-model local RPC fallback. Missing limits are absent rather than synthesized as Unlimited.
• Claude account limits prefer the official Claude Code statusLine 5h/7d fields. When Claude Code is not producing statusLine updates, a read-only compatibility fallback can query the same account windows using the existing Claude Code access token. A model-scoped target such as Fable appears only when one of those provider-reported sources includes it; WhereMyTokens does not infer missing limits.
• When Claude Code login expires or is rejected, WhereMyTokens shows one Windows notification and an in-app action that opens the official claude auth login flow. It watches for the credential change and retries automatically, without refreshing tokens or writing credentials itself.
• Optional draggable Windows taskbar mini display uses two physical lines for normalized 5h/7d entries. Two represented periods use one line each; a single represented period can use both lines, with configurable 1-3 blocks per line and compact +N hidden-target cues.
• Built-in English, Japanese, and Simplified Chinese UI with a Settings → General → Language selector.
• Codex reset-credit availability can appear as a separate Plan Usage target, with Rich, Simple, or hidden display modes in Settings.
• Active and recent session tracking from local provider data.
• Today and all-time token, cost, cache, model, and call summaries.
• Activity heatmaps, rhythm charts, model usage, and tool breakdowns.
• Git output metrics for persistently tracked repositories, independent of recent session membership, with reversible project exclusions.
• Persistent totals use the source-attributed usage-index.sqlite. Request detail is retained for 8 days, hourly precision for 35 days, daily precision for 180 days, and monthly totals indefinitely. First indexing stays responsive and labels incomplete coverage; Reset index discards indexed history and rebuilds only from currently available provider logs.
• Local-first storage with no cloud sync or telemetry.

Privacy

WhereMyTokens reads local provider files and calls only the enabled providers that require a live usage request. It does not upload session logs, run cloud sync, or ask you to paste API keys.

Claude quota monitoring prefers the local Claude Code statusLine. When no fresh statusLine quota exists and Claude Code credentials are available, the Desktop compatibility fallback loads ~/.claude/.credentials.json, extracts the existing access token plus plan metadata, and sends only the access token to the fixed HTTPS host api.anthropic.com for a quota request. It ignores the refresh-token property, never refreshes credentials, and never writes the credential file. One request may occur on app launch; during the same run, requests are limited to once per 15 minutes, apply timeout/response-size limits and 429 backoff, and do not retry a rejected access token unless it changes. Cached compatibility quota is bound to a one-way token marker and expires at the earlier of its reported reset time and a 30-minute cap.

Codex live usage and reset-credit checks use ~/.codex/auth.json only for direct OpenAI/ChatGPT requests when Codex is enabled. Reset-credit cache stores counts, expiry times, fetch status, source labels, a hashed auth marker, and the auth file modified time.

Antigravity uses local RPC only. It does not use Google OAuth, refresh tokens, Google cloud usage endpoints, or offline database fallback.

See Privacy and Security for the full data-source list.

More

License

MIT