open source · MIT★ star it on GitHubfound a bug, or want an agent supported?open an issuebuilt in the open, receipts included
skip to content
tokenchitv0.10.0 · MIT

Supported agent

Your Gemini CLI usage, as a file in your repo.

tokenchit reads the Gemini CLI logs already on your machine and renders one embeddable card straight into your repository. The card is a file you commit, not a URL you depend on — nothing to rate-limit, nothing to go down.

$ npx -y @tokenchit/cli@latest generate

Free and MIT. No account is needed to read your own numbers — publishing to the board is a separate, opt-in command.

[ 01 ]

What it reads

Gemini CLI records each model turn in a chat recording, one JSON object per line. Only turns written by recent versions carry a tokens object; the rest of the line — the prompt, the reply, the project hash — is never read.

Source~/.gemini/tmp/*/chats/*.jsonl

Nothing else is read, and nothing is sent. tokenchit sync and tokenchit recap make no network request at all; five tests in the repo fail on every push if that stops being true.

[ 02 ]

What it cannot tell you

Older sessions carry no counts at all

Token recording is a recent addition upstream, so an installation whose recordings predate it is genuinely uncountable rather than empty. Measured on one machine while the adapter was written: 2 of 2,141 session files carried any token field. tokenchit reports that as a partial state rather than showing a confident zero, and counts what it can actually read. Gemini's own models have no public per-token price yet, so they contribute tokens and no cost.

Equivalent cost is not what you paid either. It is what these tokens would cost at list API rates, and most agent usage runs under a subscription where no per-token charge ever happens.

[ 03 ]

The other agents

One command covers all of them at once, and the card shows the mix.

Detected and deliberately unsupported: Copilot CLI records only a live context gauge, so there is no per-call token count to read.

Read your own numbers

One command. It finds your agents, shows your stats and writes the card. Publishing is a separate step you have to ask for.

$ npx -y @tokenchit/cli@latest generate

Or tokenchit sync on its own to see the figures without writing anything. Source at github.com/iyashjayesh/tokenchit.

Who is burning the most?

Ranked by tokens, from developers who chose to publish. The two windows disagree on purpose — one rewards the last month, the other the whole history.

Last 30 days

All time

Top 8 of each. A means the GitHub identity was proved; everything else is self-reported.

See the full board →