Claude Code says nothing about how fast you are spending your subscription limits until one of them stops you. This watches them.
A tray icon with two rings — the five-hour session on the outside, today's share of the weekly budget inside — a window with the history, and, if you want one, a line in Claude Code's own status bar. The part worth having is the advice: it works out how much may still go today to land exactly on the weekly reset, rather than running dry on Thursday.
| Overview | History |
|---|---|
![]() |
![]() |
| Models | Settings |
![]() |
![]() |
Take the archive for your platform from the
releases, unpack it
anywhere, run claude-status, and press Register in Claude Code under
Settings → Data source. Restart your Claude Code sessions afterwards.
Registration edits one key in ~/.claude/settings.json, keeping a backup and
leaving a third-party status line alone unless told to replace it.
On Linux the tray icon needs system libraries:
sudo apt install libgtk-3-dev libayatana-appindicator3-dev libxdo-devThe status line only reaches Claude Code started from a terminal; a session hosted by an editor draws none. When it goes quiet, the limits are asked for directly instead — which starts a short-lived Claude Code of its own, no more often than every 15 minutes. Both the interval and the whole thing can be turned off under Settings → Data source.
The status line template is edited in the window, with a live preview, ready presets and the list of placeholders.
Settings, the database and its backups live in %APPDATA%\claude-status on
Windows, ~/.local/share/claude-status on Linux and ~/Library/Application Support/claude-status on macOS. CLAUDE_STATUS_DIR overrides it.
The interface follows the system language, and can be switched to English or Russian.
Everything the window does can also be done from a shell, if you want it
scripted: claude-status --help lists the commands.
cargo build --releaseThe binary lands in target/release/ and can be moved anywhere.



