InflaTOKEN

A tiny, native, local-only macOS menu bar app that watches your Claude Code token usage inflate in real time.

---

InflaTOKEN sits quietly in your menu bar and tells you, at a glance, how many tokens (and roughly how many dollars) your Claude Code sessions have burned through today, across however many concurrent sessions you have open.

Why

InflaTOKEN shows Claude Code usage information at a glance, live, with a trend chart and a per-model breakdown, and it does it entirely on your machine. Claude Code already tracks this in /usage, but that's a command you have to remember to run, in a terminal you have to switch to.

Features

• Live menu bar count: Today's token total
• Today / Active cards: Today's tokens + estimated cost, and how many Claude Code sessions are currently active
• Active sessions list: See what each of your concurrent sessions is doing right now, by project
• 7 / 30-day trend chart: Hover any bar to see that day's exact token count
• Per-model breakdown: Which models are actually costing you money
• Share card: Generate a beautiful image of today's stats and share it via the native macOS share sheet
• Update check: A quiet link in the popover when a newer release exists
• Zero configuration: No API keys, no sign-in, no setup.

Preview

Both the trend chart and the share card support a bar or line style, and a 7 or 30-day range. Whatever you pick in the popover is what the share card renders too.

7d · bar	7d · line
30d · bar	30d · line

Share card, 7d · bar	Share card, 7d · line
Share card, 30d · bar	Share card, 30d · line

Privacy

InflaTOKEN reads Claude Code's local session transcripts (~/.claude/projects/**/*.jsonl) and nothing else. No telemetry, no analytics, no phoning home: your usage data never leaves your Mac. All state (a small tail-position cache, so it never has to re-read your entire history on every launch) lives in ~/Library/Application Support/InflaTOKEN/.

The one network request InflaTOKEN makes is a check against GitHub's public release API (once at launch, then once a day) to see if a newer version exists. No usage data, no identifiers, nothing about you or your machine is sent. It only ever shows you a link to the release page; it never downloads or installs anything on its own.

How it works

Claude Code writes one JSON line per assistant turn to a session transcript file. Each line carries a usage block (input/output/cache tokens) plus a requestId and message.id. InflaTOKEN tails those files incrementally (only reading newly appended bytes, not the whole file on every poll) and aggregates by day, model, and session, including per-session-per-model, so the "Active sessions" list can show an accurate estimated cost per session, not just tokens.

Daily aggregates (and the request-dedup keys scoped inside them) are retained for 90 days and pruned after that, which is also the practical ceiling on how far back the trend chart's "30 days" view can show.

Estimated costs use a small hand-maintained pricing table (Sources/InflaTOKEN/Models/PricingTable.swift) and cache-token pricing approximations. They're estimates, not billing. Claude Pro/Max subscription usage isn't metered in dollars the way API usage is; this just gives you a rough API-equivalent sense of scale.

Requirements

• macOS 14 (Sonoma) or later
• Claude Code writing session logs to ~/.claude/projects/
• Internet access is entirely optional: only the update check needs it, and it fails silently if you're offline

Installation

Download

Grab the latest .zip from Releases, unzip it, and drag InflaTOKEN.app into /Applications.

There's no Apple Developer ID signing this, so macOS will refuse to open it the first time. Right-click (or Control-click) the app → Open → Open again in the dialog that follows. You only need to do this once.

To have it launch automatically at login, open it and turn on Launch at Login.

Building from source

git clone git@github.com:o-ba/InflaTOKEN.git
cd InflaTOKEN

No Xcode project file is needed. This is a plain Swift package. Open it directly in Xcode with:

open Package.swift

or build from the command line:

swift build              # debug build, for development
swift test                # runs the test suite
swift build -c release   # release build
./Scripts/build-app.sh   # wraps the release binary into a proper .app bundle

If swift test fails with no such module 'Testing' (or 'XCTest'), your xcode-select is pointed at the standalone Command Line Tools rather than a full Xcode install. Either run sudo xcode-select -s /Applications/Xcode.app/Contents/Developer, or scope it to just this command: DEVELOPER_DIR=/Applications/Xcode.app/Contents/Developer swift test.

Contributing

Contributions are welcome and encouraged.

License

MIT, see LICENSE.

---

Created with ❤️ by Krawoli in 2026