Free & open source · for Claude Pro & Max

Your Claude limits,
in the menu bar

Tokease shows your 5-hour & weekly limits for Claude in the menu bar. Zero config: it reads only what official Claude apps already publish on your Mac. No token read, no hidden API call.

5-hour 0% Weekly 0%
2
limits at a glance
0
tokens read
100%
local, on your Mac
$0
price, forever

Your remaining 5-hour and weekly limits, one glance away

Two rings fill as you spend your 5-hour and weekly windows, right next to the clock. In short, a lightweight Claude rate limit monitor for your Mac: you see the wall coming before you hit it.

Tokease menu bar dropdown on macOS showing the Claude 5-hour limit at 77% and weekly limit at 35% with reset times
Your 5-hour and weekly limits, one click away in the menu bar.

Up and running in a minute

Install the app and keep the Claude desktop app open. That's it. No account, no API keys, nothing to configure.

Install Tokease

One line: brew install tpatrouillat/tap/tokease. Or clone the repo and run the install script to audit every line first.

Let it find your data

If the Claude desktop app is running, Tokease auto-detects the quota history it refreshes about every 5 minutes. Nothing to wire, nothing to configure.

Read the rings

Your two rings light up in the menu bar, 5-hour and weekly, refreshed while the Claude desktop app runs. Bonus for CLI users: wire the included statusline script into Claude Code to add reset countdowns.

Read it before you run it.

The app is one 865-line Python file, plus a 158-line script if you want reset countdowns. No HTTP client is imported anywhere in it, so there is no update check, no telemetry, no crash reporter. That is not a promise, it is something you can verify in about ten minutes.

Token-free by construction, not by promise.

Tokease reads two local files, both written by official Claude apps for their own use: the quota history the Claude desktop app refreshes while it runs, and the documented rate_limits fields Claude Code 2.1.x and later hand to their statusline script. It reads exactly those, and nothing else. It never reads your OAuth token, never opens your Keychain, and never calls any Anthropic endpoint.

No server, no analytics, no telemetry, no phone-home. There is no token to misuse and nothing that leaves your Mac. The whole app is one MIT-licensed Python file of about 850 lines: read tracker.py on GitHub and verify it yourself.

No token, no Keychain

Tokease never reads your OAuth token and never opens the Keychain. There is no credential for it to misuse.

100% local

Runs entirely on your Mac. No backend, no cloud, no account. Nothing to breach.

Fully auditable

One short Python file, MIT-licensed, zero telemetry. Read it, fork it, run it from source in 30 seconds.

Free. Forever.

No tiers, no trial, no upsell. Open source under the MIT license.

MIT License
$0 / forever
  • All features, no paywall
  • Open source: read, fork, contribute
  • No account, no telemetry, no token read
  • Requires a Claude Pro or Max plan (Claude Desktop, or Claude Code ≥ 2.1.x)
Install Tokease

Like it? A GitHub star is always welcome.

Questions, answered

Everything people ask before installing.

Is Tokease free?
Yes. Completely free and open source under the MIT license. There is no paid tier, no trial, and no account to create.
Is it safe to use a Claude usage tracker?
It depends on what the tracker reads. Trackers that read your OAuth token from the Keychain act as you against Anthropic's API, which can put your account at risk. Tokease never reads your token. It only reads local files official Claude apps already write on your Mac, and you can verify that yourself: exactly what it reads, or the code itself.
Does Tokease read my Claude token or call any hidden API?
No. Tokease never reads your OAuth token, never opens your Keychain, and never calls any Anthropic endpoint. It only reads usage data official Claude apps already write on your own Mac: the Claude desktop app's quota history, and the documented rate_limits fields Claude Code hands to its statusline. Token-free by construction, not by promise.
Does it work on the free Claude plan?
No. Tokease requires a Claude Pro or Max plan, because Anthropic only exposes these quota windows for paid subscribers. Free, Team, and Enterprise plans are not supported.
Where does Tokease get its numbers?
From two local files written by official Claude apps. The Claude desktop app refreshes a quota history about every 5 minutes while it runs. Claude Code 2.1.x and later hand the documented rate_limits fields to their statusline, which adds reset times. No token read, no hidden API call.
Claude Code already shows my usage in /usage and the statusline. Why an app?
Same numbers, different surface. /usage and the statusline show your limits while you're looking at the terminal, which is when you least need the reminder. Tokease shows them in the menu bar while you're in your editor or a browser, and keeps the last known value (flagged stale) in between.
How is this different from the other menu bar trackers?
They make different trade-offs, and several are excellent. The one that shaped Tokease is size: the app is a single 865-line Python file, plus a 158-line script if you want reset countdowns. No HTTP client is imported anywhere in it, so there is no update check, no telemetry, no crash reporter. In a large codebase "it does not phone home" is a promise you accept. Here it is something you can verify yourself in about ten minutes.
How is this different from ccusage?
ccusage parses your local Claude Code JSONL log files to estimate token spend, a great breakdown of what you already used. Tokease shows the complementary thing: the limit you have left. Your remaining 5-hour and weekly windows, live in the menu bar.
Does it work with Claude Desktop or Cowork?
Yes. If the Claude desktop app is running, Tokease reads the quota history it refreshes about every 5 minutes. Your limits are account-wide, so the rings cover everything you consume: claude.ai, Cowork, the VS Code extension and the CLI.
I work in the VS Code extension. Does Tokease still update?
Yes, through the Claude desktop app. The VS Code extension panel never runs statusline scripts (claude-code#55643), so keep the desktop app open (or run claude in a terminal) and the rings stay fresh.
How fresh are the numbers?
With the Claude desktop app running, the rings refresh about every 5 minutes. A Claude Code terminal session refreshes them too and adds reset countdowns. When neither runs, Tokease shows the last known value with a timestamp and flags it stale after 15 minutes, so you never mistake an old percentage for a live one.
How do I install Tokease?
Run brew install tpatrouillat/tap/tokease, or clone the repo and run the install script. If the Claude desktop app is running, you are done. Optionally wire the statusline capture script into Claude Code (a one-line settings change) for reset countdowns (see the Install section).
I installed it but I don't see the icon. Where is it?
Tokease is probably running fine and your menu bar is full. On notched MacBooks, macOS hides overflow menu bar icons without any indicator. Quit a menu bar app you don't need (or use a manager like Ice or Bartender) and the rings appear. The percentage-only display mode in Settings also narrows Tokease's footprint.

Pick your path

Both options are free. Requires macOS and a Claude Pro or Max plan.

Homebrew Recommended

One command. Installs a self-contained environment, with no Apple Developer warnings.

$ brew install tpatrouillat/tap/tokease
$ brew services start tokease
The second line starts it and brings it back at every login. Zero config if the Claude desktop app is running. Optional: wire the statusline capture script for reset countdowns, see the setup guide.

Build from source

Audit every line. Clone, install, run. About 30 seconds. Needs Python 3.10+ (the Homebrew path ships its own).

$ git clone https://github.com/tpatrouillat/tokease.git
$ cd tokease
$ bash install.sh

Get a heads-up on new releases

No email, no newsletter, no account to hand over. That would be off-brand for a tool that never reads your token. Watch the repo and GitHub tells you when a new version ships, or when a change in what Claude apps publish locally means Tokease has to follow.

On GitHub, choose Watch → Custom → Releases to get only what matters.