Know when your Claude plan runs out. Before it does.
BoltGauge is a usage gauge for people who code with Claude, Codex or Grok on a subscription. A small agent runs on your PC, reads the transcripts your coding tools already keep there, takes the counts, and leaves the words. It counts Grok usage from the Grok CLI's session files as well, and reads plan limits for Claude and Codex only. Your dashboard shows how much you have used, what it would have cost at API prices, and when today's window fills up at your pace. One file. No installer.
Download for Windows (x64), 98.5 MB- Version
- 0.2.7
- Size
- 103,335,192 bytes
- Signed by
- Patrick Williams
SHA-256
786ca36eafb262b86284926c00e8b2fd
Windows will probably warn you the first time. Here is what to look for. The file is signed by me, Patrick Williams, the person behind BoltGauge, and Windows checks that signature when you open it. A new release still gets the “Windows protected your PC” screen for its first weeks, until enough people have run it.
When you see that screen, read the Publisher line. It should say Patrick Williams. Click More info, then Run anyway.
If the screen says the publisher is unknown, stop. That file is not mine. The check at the foot of this page tells you for certain, before you run anything.
What happens when you open it
A window opens and asks first.
Your browser opens so you can approve this machine.
The window says installed. Close it.
What it sends, and what it never sends
For each request: the token counts, the model name, the provider, the name of the folder the session ran in (never the full path), the time of the request, the provider's session id, a key that stops the same request, or the same upload, counting twice, and whether a sub-agent made the request. No cost is sent; the server works the cost out from the token counts when a record arrives. For each plan limit: the percent used, the window length, the reset time, the plan name and the time of the reading, with each window's kind and group, a severity word, the model's display name where a window is per model, and whether the window is active; for Codex, the limit's id and name, a line number, and a scrambled code for the reading's source, used only to keep readings in order. Each Claude limit reading carries a short scrambled code that says which Claude sign-in it belongs to. Each Codex limit reading carries the same kind of code for the Codex sign-in. Neither code can be turned back into your account.
It never sends your words, your code, or your files.Not what
you typed, not what the model answered, and not the contents of any file. To
read your plan's limits it uses your Claude
sign-in with Anthropic directly. That sign-in never reaches BoltGauge and is
never written to a log. To read your Codex plan's limits it asks the Codex
program on your machine, which talks to OpenAI with its own sign-in; the agent
never reads that sign-in. To tell your Claude sign-ins apart it reads one
value from ~/.claude.json, your account id, and scrambles it; for
Codex it scrambles the account id Codex reports. Your email address and
display name stay on your machine.
The window shows this statement in full before anything installs. The long version is in the privacy policy and the terms of service.
Check the file
Get-FileHash .\boltgauge-agent-win-x64.exe -Algorithm SHA256
The result must match the SHA-256 above. If it does not, delete the file and tell me.