How to use
Before you install
QuotaLens authenticates with your provider's session cookie and reads undocumented status endpoints. It only observes — it cannot raise, bypass, or extend a limit — and running it is your decision.
That is automated access, which Anthropic's Consumer Terms, section 3(7), prohibit. A subscription cookie is not an API key, and there is no carve-out for reading your own usage. You are the one accepting that risk, not me.
Install
pipx install git+https://github.com/amitshcc/quotalens
quotalens auth # paste your claude.ai session cookie once
quotalens start
open http://127.0.0.1:8787
Requires Python 3.11+ and a Claude Pro or Max subscription. macOS, Linux and Windows, each tested in CI on every push; the Windows credential store is not yet verified by hand. Not on PyPI yet — you install from the repository.
Where the cookie lives
Nowhere else: not the config, not the log, not the database. It is
redacted from error output (how,
in the source), and quotalens config list prints every setting and where it
came from, and never the cookie.
As a service
quotalens service install # macOS LaunchAgent, or a systemd user unit
Every file it writes is printed, so it can be undone by hand. A second account
is a profile: quotalens --profile work start gets its own keyring entry,
database and port.
What you do with it
- Burn rate and a verdict. Read the rate mid-session and know if you make the reset.
- Your week, in sessions. See how many full sessions the weekly budget still buys.
- The history. Sort past windows by consumption; click the expensive one.
- Local only. All data stays in SQLite and the OS keychain. The dashboard binds to localhost with no option to expose it.