OpenToken Monitor

Every AI coding quota, in your menu bar.

Live usage limits, exact per-project costs, and time-to-limit alerts for Claude Code, Codex, and Antigravity — read from your own machine, never a SaaS dashboard.

Download · What it does · Features · How it works · Privacy · FAQ

_{30 seconds of v0.4.1 on macOS, running on real usage.}

🎯 What it does

You run more than one coding agent. Each has its own quota window, its own reset timer and its own pricing page, and none of them tells you you're about to hit the wall until you do. OpenToken Monitor watches all of them from your menu bar.

Here is what the demo above walks through:

1. Rings in the menu bar. Each provider gets its logo wrapped in two usage rings: the outer ring is its primary window (Claude 5-hour, Codex session, Antigravity 5-hour), the inner ring its secondary window (Claude 7-day, Codex weekly, Antigravity daily). They turn green → amber → red as you burn through them, so a glance is usually enough.
2. Click a ring to open that provider. You land on its detail page: every quota window with a reset countdown, a FULL IN forecast when your current pace will hit 100 % before the reset, today's and 30-day cost, cache-hit rate and how much prompt caching saved you.
3. Overview. Claude Code, Codex and Antigravity side by side, with live/local status, usage and a cost sparkline for each.
4. Projects. Exact spend per working directory and per CLI session, read from the session logs your CLIs already write.
5. Compare. Spend share across providers plus side-by-side usage, spend, tokens and burn.
6. All of it local. The numbers are computed on your machine from your own logs and your CLIs' own sign-ins. No account, no telemetry, no proxy.

When the window is closed, the app keeps working in the background: the rings stay current and alerts fire before a window fills or a budget overruns.

Get started in a minute

1. Download the installer for macOS, Windows or Linux (details).
2. Use the CLIs you already have. Sign in to claude, codex or Antigravity as usual; OpenToken Monitor finds their logs and credentials on its own.
3. Look at your menu bar. The rings appear on first launch. There is nothing to configure.

🚀 Features

🧠 How it works

flowchart TB
  subgraph SRC["💻 Your machine"]
    direction LR
    CL["~/.claude/projects<br/>session logs"]
    CX["~/.codex/sessions"]
    AG["Antigravity logs"]
  end

  subgraph LIVE["🌐 Live limits (optional)"]
    direction LR
    AN["Anthropic usage API<br/>(your CLI's OAuth token)"]
    OA["ChatGPT / Codex usage"]
    LS["Antigravity language server<br/>(127.0.0.1)"]
  end

  subgraph CORE["🦀 Rust core"]
    direction TB
    TRG["Poll scheduler<br/>+ file watchers"]
    SCN["Incremental log scanners"]
    PRV["Provider adapters"]
    AGG["Aggregator"]
    DB[("SQLite<br/>snapshots · history · costs")]
    FC["Limit forecast"]
    SES["Session & project usage"]
    HOOK["Post-refresh hook"]
    ALR["Alert engine"]
  end

  subgraph UI["⚛️ React UI"]
    direction LR
    STO["Zustand stores"]
    VIEWS["Overview · Detail · Projects<br/>Compare · Widget · Settings"]
  end

  subgraph DESK["🖥️ Desktop"]
    direction LR
    BAR["Menu-bar ring badges"]
    NOTE["Notifications"]
  end

  SRC --> SCN --> PRV
  LIVE --> PRV
  TRG --> AGG
  PRV --> AGG --> DB
  DB --> FC
  SCN --> SES
  AGG --> HOOK
  HOOK --> BAR
  HOOK --> ALR --> NOTE
  FC --> ALR
  DB -- "Tauri commands" --> STO
  SES -- "Tauri commands" --> STO
  HOOK -- "usage-updated event" --> STO
  STO --> VIEWS

1. Collect. Scanners read the CLIs' own session logs incrementally (only new bytes are parsed). When your CLI is signed in, the matching adapter also fetches the live quota — using the token the CLI already stored, never one you paste in.
2. Store. Each refresh writes the latest snapshot, a utilization history point, and daily per-model costs to a local SQLite file.
3. Derive. The forecast fits a line through the last 30 minutes of history; sessions are rolled up into projects by working directory; costs use the rate tables in pricing.rs.
4. Surface. One post-refresh hook updates the menu-bar badges, evaluates alerts, and tells the UI to re-render — whichever path triggered the refresh (timer, file change, or you).

Full module map and data flow → ARCHITECTURE.md

Data sources

When a live fetch fails, the last good snapshot stays on screen marked stale, and the provider falls back to local logs.

📸 Screens

_{Each provider's logo sits inside its usage rings — outer ring: primary window (Claude 5-hour), inner ring: secondary window (Claude 7-day). Click a ring to open that provider.}

Overview every provider at a glance	Provider detail windows, resets, forecast, cost	Compare spend share and burn side by side
Sessions exact cost per CLI session	Settings theme, refresh, alerts, budgets, menu bar	Widget mode always-on-top gauges
Projects spend by working directory across Claude and Codex		Menu-bar badges logo + usage rings

The full menu bar

The Windows taskbar

📦 Install

Grab the installer for your OS from GitHub Releases:

Then just sign in to the CLIs you already use (claude, codex, Antigravity). OpenToken Monitor finds their logs and credentials on its own — there is nothing to configure.

xattr -dr com.apple.quarantine /Applications/OpenTokenMonitor.app

git clone https://github.com/Hitheshkaranth/OpenTokenMonitor.git
cd OpenTokenMonitor
npm install

npm run tauri dev            # run with hot reload
npm run tauri build          # production build for this platform
npm run tauri:build:win      # Windows NSIS installer
npm run tauri:build:mac      # macOS app bundle + installer

⌨️ Usage

Menu-bar modes (Settings → Menu bar): Usage % shows the ring badges, Today's cost adds today's spend beside them, Off keeps the plain app icon.

🔒 Privacy

• 🏠 100 % local. Snapshots, history and costs live in a SQLite file in your OS app-data folder.
• 🔑 Your CLIs' credentials, read-only. Tokens are read from where claude and codex already keep them; requests go straight from your machine to the provider.
• 🚫 No telemetry, no analytics, no crash reporting.
• 🔤 No CDN. Fonts ship inside the app.
• 🔍 Verify it. The only outbound hosts are api.anthropic.com, chatgpt.com and auth.openai.com (plus GitHub Releases if you enable the updater). Antigravity is read from a server on 127.0.0.1. The webview's Content Security Policy enforces the same list.
• 🧹 Reset by deleting usage.db from the app-data folder (%APPDATA%\com.opentokenmonitor.desktop\ on Windows, ~/Library/Application Support/com.opentokenmonitor.desktop/ on macOS).

❓ FAQ

🧱 Built with

Rust — Tauri 2 · Tokio · Reqwest (rustls) · Rusqlite (bundled SQLite) · Notify · image TypeScript — React 19 · Zustand · Recharts · Framer Motion · Lucide · Vite 7

🗺️ Roadmap

• Budget alerts with native notifications
• Export to CSV / JSON / PDF
• Per-provider refresh cadence and thresholds
• Time-to-limit forecasting
• Exact per-project and per-session costs
• Menu-bar ring badges
• Keep project history beyond Claude Code's 30-day log cleanup
• Claude Code statusline integration and a local CLI / JSON state file
• Per-provider tray badges on Windows
• Per-provider tray badges on Linux
• OpenCode, Gemini CLI, Copilot CLI and Cursor adapters

Have an idea? Open an issue.

🤝 Contributing

1. Read ARCHITECTURE.md for the module map.
2. New provider: implement the UsageProvider trait in src-tauri/src/providers/<name>/ and register it in registry.rs.
3. Pricing update: edit src-tauri/src/pricing.rs and bump the review date at the top.
4. Before opening a PR:

cargo fmt   --manifest-path src-tauri/Cargo.toml --all -- --check
cargo clippy --manifest-path src-tauri/Cargo.toml --all-targets -- -D warnings -A unused-mut
cargo test  --manifest-path src-tauri/Cargo.toml
npm run build