-
Notifications
You must be signed in to change notification settings - Fork 12
FAQ
No. It reuses the OAuth token Claude Code already created (in
~/.claude/.credentials.json or the macOS Keychain). If the claude CLI
works, the widget works. It never has credentials of its own.
The usage fetch hits a lightweight status endpoint, not a model. The only feature that calls a model is the AI weekly report (a single short Claude Haiku call, cached for an hour) — and it silently no-ops if you'd rather it didn't run.
No. It talks to Anthropic (the same endpoints Claude Code uses) and reads local files. Raw prompt text is redacted from the CLI and the localhost API. The only non-Anthropic network call is the optional news ticker, which is off by default.
Linux, macOS, and Windows — one pip install, Qt bundled. No apt,
brew, PyGObject, or rumps required.
Same numbers, always-on-top, no browser. Plus live tokens/min, a per-turn cost ticker, forecasts, heatmaps, per-model cost breakdown, an AI weekly summary, CLI/API surfaces, and webhooks.
Yes: claude-usage --detach double-forks and logs to
~/.cache/claude-usage/widget.log. For autostart, see Installation.
Drag with left-click to move (the spot is remembered); scroll to resize (0.6×–2.0×, remembered). Or right-click → OSD Position ▸ for corner presets. See Usage.
Almost always a transient API rate-limit. Fixed to degrade gracefully in
v0.8.3+; raise refresh_seconds if you still see it. See
Troubleshooting.
Yes — that's what --field and the localhost JSON API are for. See
Shell Integrations.
Right-click → Theme ▸, or set "theme" in config.json. 11 options —
see Themes.
~/.config/claude-usage/config.json. It's created and updated
automatically as you use the menu; you can also hand-edit it. Full key list
in Configuration.
pip install --user --upgrade claude-usage-widget (or brew upgrade claude-usage-widget), then restart the widget. An Update available
banner also appears in the right-click menu when a new release lands.
See Troubleshooting → "OSD not visible".