Hypermile

Free tool · Local only

See where your tokens go. Nothing leaves your machine.

hypermile-audit is the free CLI behind Hypermile’s Gauge tier. One command reads your local Claude Code and Codex transcripts and prints a plain-English breakdown of the week — categories, waste, estimated savings range. No account, no upload, MIT licensed. As of August 2026 this is the fastest way to measure before you change anything.

Install

Two advertised commands. Prefer Node for a one-shot run; prefer Cargo if you already have a Rust toolchain.

$ npx hypermile-audit
$ cargo install hypermile-audit
$ hypermile-audit

Source and releases: GitHub. npx may download the binary once from GitHub Releases; the audit run itself makes no network calls.

What it reports

Point it at your local transcript directory (Claude Code’s ~/.claude by default, including inside WSL2) and it scans recent sessions. The terminal report covers:

Useful flags: --days 30, --project, --json, --html for a shareable file, and --redact-paths if you post a report. Full flag list is in --help.

Sample report · figures illustrative

Same layout as the homepage demo (spec 01 sample). Not production telemetry, not a promise of savings on your workload.

Privacy: local-only

The audit reads *.jsonl transcripts on disk. It does not upload them, and it does not send telemetry. The printed report uses file names, tool names, and aggregate token counts — not file contents or prompt text. If you share an HTML or JSON dump, add --redact-paths so directory layout is hashed.

That is the same local-first rule as the rest of Hypermile: Gauge keeps the in-app audit on your machine; Pro compression also stays local. Cursor remains partial for the desktop app (most Cursor traffic is not interceptable by a local proxy) — the CLI only reads transcripts that already exist on disk.

Then stretch the week

The CLI is the measurement step. Hypermile Gauge — free — is that audit in the desktop app. Pro adds a cap forecast and reversible compression so the noisy parts of each prompt never reach the model. No fabricated fleet averages here; harness results live on Benchmarks.

Related

Frequently asked questions

Does hypermile-audit upload my transcripts?

No. The audit reads local JSONL transcript files on your machine and prints a report. It does not upload prompts, file contents, or usage data. The npx installer may fetch the binary once from GitHub Releases; the audit run itself stays offline.

What does hypermile-audit report?

A category breakdown of where context went (tool output, file reads, prompts, model output), waste findings such as repeated file reads and compressible logs, and an estimated savings range from those detectors. Your numbers come from your own transcripts.

How do I install hypermile-audit?

Run npx hypermile-audit for a one-shot install, or cargo install hypermile-audit if you have a Rust toolchain. Both commands are the ones advertised on this site. Source is MIT on GitHub.

Is the CLI the same as Hypermile Gauge?

Gauge is the free product tier: the in-app local audit plus this MIT CLI. The CLI is the no-app starting point. The desktop app adds the same local audit in a UI, then Pro unlocks forecast, compression, and the inspector.

Does hypermile-audit work on Windows and WSL2?

Yes. Run it on native Windows, macOS, or Linux, or inside a WSL2 distro so it reads ~/.claude where WSL2 Claude Code actually writes. It does not need a Hypermile account.