Last updated · 2026-05-25

Nothing leaves your machine.

tokenlens is a local CLI and a local Claude Code plugin. It reads files on your own disk to compute a breakdown of where your context tokens went, and it writes those numbers to your terminal. There is no server, no analytics, no telemetry, and no account.

§ 01What tokenlens reads

The tool reads the following files on the machine it runs on, and only when you explicitly invoke it:

The contents of these files stay on your machine. tokenlens computes numbers from them, prints those numbers to your terminal, and writes a local log of hook decisions to ~/.claude/tokenlens.log so you can audit what the plugin did.

§ 02What tokenlens does not do

The doctor --fix subcommand will delete stale plugin version directories and duplicate skill symlinks inside ~/.claude/, but it refuses to operate on any path outside that directory and logs every deletion with its full path before performing it.

§ 03Configuration

A telemetry field exists in ~/.claude/tokenlens.json and ships set to "off". There is currently no telemetry implementation behind it; the field exists as a stub so that any future opt-in collection (e.g., anonymized aggregate cost statistics) will land behind it as an explicit choice. If we ever ship a telemetry feature, this page will be updated, the field will default to off, and the source will be visible in the public repo before the feature lands.

§ 04The homepage

This site (tokenlens.bouncei.dev) is hosted on GitHub Pages. It is a static HTML file with no first-party JavaScript that contacts any analytics provider. The page loads three font families from Google Fonts; if you want to avoid the Google CDN, you can install tokenlens directly from npm and never visit this site again.

§ 05Source & license

Every claim on this page is verifiable in the source code at github.com/bouncei/tokenlens. The project is MIT-licensed; you are free to audit, fork, or remove any behavior you disagree with.