Tokease banner
tpatrouillat tpatrouillat

Tokease

Development community

Description

macOS menu bar app showing your remaining Claude 5-hour and weekly usage limits. No token read, 100% local.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

Tokease

Tokease

A lightweight macOS menu bar app showing your Claude 5-hour and weekly limits
One 970-line Python file, plus a 178-line script. No HTTP client is imported anywhere in it, so you can check what it does before you run it.

CI License: MIT Platform: macOS No telemetry

![Tokease menu bar dropdown showing the Claude 5-hour and weekly limits with reset times](docs/screenshot.png)

brew install tpatrouillat/tap/tokease
brew services start tokease      # starts it now, and at every login

Requires macOS 12 Monterey or later and a Claude Pro or Max plan. Zero config if the Claude desktop app is running. [Other install paths below.](#install-from-source)

Why Tokease

Tokease reads only two local files: the quota history the Claude desktop app writes on your Mac, and the `rate_limits` data Claude Code hands to its statusline, which the 178-line capture script saves to `~/.tokease`. No OAuth token read from the Keychain, no hidden API call, no User-Agent spoofing.

That is a sentence any tracker can write. What you can actually check is the size. The app is one 970-line Python file, plus a 178-line capture script if you want reset countdowns. The import block at the top of [`tracker.py`](tracker.py) is the whole dependency story, and there is no HTTP client in it, so there is no update check, no telemetry and no crash reporter. The only subprocess it spawns is `osascript`, for launch-at-login. Open