tokmeterGet Tokmeter The local ledger for AI work · v1.19.4
One ledger for every coding agent you run. Know where the tokens went, and the work behind them, from files already on your disk.
SourcesSession files from 25 integrations
The meterPriced where a price is known
The ledgerRows by project, model and day
Read, don’t requestLocal first
Your agents already write everything down. Tokmeter reads those files where they lie, keeps every source in its own column, and seals each finished day so history stays put.
A day on the ledger
Tokmeter works around your routine, not the other way round. Scroll from the first session to the moment the day is sealed.
| Time | Agent · project | Tokens | Est. |
|---|---|---|---|
| 09:12 | Claude Codeproduct · Model A | 486,210 | $1.92 |
| 11:40 | Codexproduct · Model B | 312,480 | $1.14 |
| 14:05 | Cursorresearch · Model C | 201,930 | $0.61 |
| 17:30 | Gemini CLIside project · Model A | 247,700 | $1.15 |
| Day total | 1,248,320 | $4.82 | |
09:12Claude Code
Three sessions on the product repo, read from the transcripts the agent already wrote. Nothing to connect, nothing to sign in to.
Input, cached input and cache writes stay in their own buckets.
11:40Codex
A different agent, a different file format, the same ledger. Response receipts are read as the tool wrote them.
Reasoning is its own bucket wherever the source reports it.
14:05Cursor
Some tools keep their history in SQLite rather than files. Tokmeter reads those databases too.
Missing data stays missing. Nothing is invented to fill a gap.
17:30Gemini CLI
The side project gets its own column, so it never hides inside the day’s total.
Merge, rename, tag or hide projects with aliases.
23:59Sealed
At midnight the day is sealed with the prices it was billed at. A later price change won’t rewrite it, and a thread you delete before then still counts.
Sealed days are immutable. Shrinking one takes an explicit, forced rescan.
One ledger · your way in
01Command line
An overview, then models, projects, days and a narrative digest. Every report takes the same filters.
--today, --week, --since on every report--project to narrow to one codebasetokmeter quota$ tokmeter projects --today
Today · by project
product 798,690
side project 247,700
research 201,930✦Projects, not just totalsIllustrative output
02macOS menu bar
Your working day in the menu bar, read from the same local daemon as everything else.
✦Actual app renderSynthetic demo data
03MCP
Ask in plain words. The answer comes from the same local numbers, through tools that can only read.
Which project used the most today?
callstokmeter_projectsread-only
product, at 798,690 tokens across Claude Code and Codex. About 64% of the day.
✦No write accessIllustrative exchange
Numbers with a point of view
A paper edition, an instrument, a pocket passbook. Each one is the app’s own render of synthetic demo data.
Paper
Meter
Rams
Terminal
Passbook
Pump
Deck
Glass
Prism
Lagoon
CarbonThe small print, up front
API-equivalent estimates stay apart from tool-reported costs. Neither is automatically your provider’s invoice.
Session formats differ. Tokmeter reports what an agent writes and what its parser understands, and says which.
Local files, no provider credentials, no Tokmeter cloud account. Beyond an optional public price catalog, the only request is the Mac app’s update check.
The details
Checked against Tokmeter v1.19.4 at ae05ff9. If the source and this table disagree, the source wins.
--light skips it). The macOS app checks GitHub for updates.Tokmeter v1.19.4
npx -y @sriinnu/tokmeter@1.19.4 --todaybrew install --cask sriinnu/homebrew-tap/tokmeterbarclaude mcp add tokmeter --scope user -- npx -y @sriinnu/tokmeter-mcp serveDocumentation
Synced from the repository and wiki at the pinned revision. Search lives on every docs page.