2026-presentLinux product adaptationLinux adaptation author and maintainer
Claude Usage Tracker for Linux
The problem
The macOS tracker experience did not exist as one coherent Linux product. A port also had to reuse Claude Code login safely instead of introducing another credential store or embedding a session key in a script.
Decisions
Claude Usage Tracker for LinuxDecision 1 of 4
Decision
Combine the macOS tracker visual and statusline direction with an existing GNOME Shell extension foundation, preserving explicit upstream credit.
Consequence
The port inherits two upstream projects, and neither of them owes it compatibility.
Claude Usage Tracker for LinuxDecision 2 of 4
Decision
Let the statusline consume Claude Code session JSON from standard input while the panel keeps the OAuth token in memory for its usage request.
Consequence
The token is gone after a restart, so the panel has to treat being unauthenticated as a normal state.
Claude Usage Tracker for LinuxDecision 3 of 4
Decision
Normalize legacy and dynamic model limits, retain bounded percentage-only history, and keep cached values visible during service failures.
Consequence
History can answer questions about pace but none about absolute usage.
Claude Usage Tracker for LinuxDecision 4 of 4
Decision
Install the statusline by preserving unrelated Claude settings, creating a timestamped backup, and testing hostile terminal input and configuration projection.
Consequence
Installation is slower and harder to follow than overwriting the settings file would be.
Outcome
Linux users get one native panel and terminal view of session pace, model limits, reset times, notifications, and recent usage without duplicating their Claude login.
Evidence and scope
This unofficial port preserves credit for both source projects in NOTICE. GNOME Shell 46 is runtime-tested; 47 through 50 are declared but untested.