Gauge

You pay one flat price a month for Claude Code, and in exchange you stop thinking about cost. That's the point of a subscription. It's also how you end up with no idea which of your own projects is eating the plan, or why Thursday felt slower than Monday.

Gauge is a meter for that. One command reads the session transcripts Claude Code already writes to your own disk and turns them into a single screen: your last five hours against the biggest five-hour window you've ever had, daily bars for two weeks, and a breakdown by project, by session, and by model. If you use Codex, it reads those rollouts too, in a separate section, because that's a separate plan's quota and mixing them would be a lie.

The numbers are API-list-equivalent dollars — what your usage would cost at published API rates. It is not your bill, and Gauge says so on the screen. Subscription plans don't publish their quota mechanics, so this is the only honest common currency available. The same discipline runs through the rest of it: the "peak" window is labeled as your observed ceiling rather than a plan limit nobody has disclosed, and a model with no published rate shows token counts instead of invented dollars.

Two things it gets right that a naive script won't. Claude Code writes one line per streamed chunk, all sharing a message id, and replays them when a session resumes — summing lines over-counts badly, so Gauge dedupes by id. And subagent transcripts nest several directories deep; in testing they held roughly half the spend.

Nothing leaves your machine. No account, no telemetry, no network calls. gauge statusline puts one line in Claude Code's status bar if you want the number in view while you work.