Maxx

Maxx

Live token usage tracker for Claude Code in your terminal status line

Open Source
4.0 (6 reviews)

Gallery

About Maxx

Maxx is a status line utility that tracks your Claude Code token consumption in real time. It displays a fuel gauge style readout directly in your terminal, showing how much of your session and weekly limits you have used. The goal is to help you pace your usage so you do not burn through your allocation early in the week and end up throttled when you need it most.

Claude Code enforces two caps, a five hour session limit and a seven day weekly limit. Maxx calculates a sustainable spending rate by dividing your remaining weekly tokens by the number of five hour windows left until the reset. It then compares your actual pace against that budget and shows whether you are banking tokens or overspending. Two visual rails in the status line give you a quick read. The session rail shows your current window, green if you are under budget and red if you are burning hot. The weekly rail acts like a fuel tank indicator, changing color as you approach depletion.

The calculations pull from Anthropic's official usage endpoint, so the numbers stay accurate. Maxx also factors in per model price weighting, since Opus, Sonnet, Haiku, and Fable consume tokens at different rates. A cache hit rate display helps you understand how much of your traffic is being served from cache versus fresh inference. All of this runs locally with no data leaving your machine.

Installation is a single curl command that downloads and sets up everything. You can also clone the repository and configure manually if you prefer. The tool works across macOS and Linux terminals, including Terminal.app, iTerm2, Ghostty, Warp, Alacritty, and kitty. A slash command, /maxx, gives you a quick summary without checking the status line. The display uses plain ANSI formatting with animated digit updates when numbers change.

Maxx is open source under the MIT license. The repository is on GitHub, and the maintainer Reif is reachable at reif@thegoodproject.net. There is no paid tier or premium version. It is a utility for power users of Claude Code who want visibility into their consumption patterns without switching to a dashboard or checking manually.

The audience is developers who rely on Claude Code for serious work and want to avoid hitting limits unexpectedly. If you have ever been surprised by a throttle mid session, Maxx gives you the awareness to spread your usage more evenly across the week.

Key Features

  • Real time token balance in terminal status line
  • Session and weekly limit tracking
  • Sustainable pace calculation and comparison
  • Per model price weighting for accuracy
  • Cache hit rate display
  • Animated digit updates on changes

Pros & Cons

What we like

  • Open source under MIT license
  • All processing runs locally with no data sent out
  • Works across popular macOS and Linux terminals
  • Single command installation

Room for improvement

  • Only useful for Claude Code users
  • Requires terminal environment that supports ANSI
  • No Windows support documented
  • Depends on Anthropic usage endpoint staying consistent

Frequently Asked Questions

What is Maxx?
Maxx is an open source status line utility that tracks your Claude Code token usage in real time. It shows session and weekly consumption with visual indicators so you can pace yourself and avoid hitting limits.
Is Maxx free?
Yes. It is open source under the MIT license with no paid tier. You can install it with a single curl command or clone the repository.
How does Maxx calculate sustainable pace?
It divides your remaining weekly tokens by the number of five hour windows left until the weekly reset. It then compares your actual spend rate against that budget and shows whether you are ahead or behind.
Does Maxx send my data anywhere?
No. All calculations run locally on your machine. It reads from Anthropic's usage endpoint for accurate percentages but does not transmit your data elsewhere.

Best For

Pacing Claude Code usage across a work weekAvoiding unexpected session or weekly throttlesTracking cache hit rates for cost awarenessMonitoring token burn during intensive coding sessions

Featured in

Alternatives to Maxx

View all

Reviews (6)

M
Mia Lund Verified

Recommended without reservation

Came to Maxx after getting frustrated with what I had before. Got real value out of per model price weighting for accuracy. It handles the boring parts so I can focus on the work that matters. Found it works best for avoiding unexpected session or weekly throttles. No regrets so far.

5/7/2026 15 found this helpful
W
William Souza

Good, with a few caveats

Picked Maxx for the price, stayed for the quality. The per model price weighting for accuracy is more useful than I expected. It would be a five if not for only useful for claude code users. Glad I made the switch.

4/25/2026 14 found this helpful
Q
Quinn Almeida

Does the job, a few gripes

Maxx solves a real problem for me without making a fuss about it. Got real value out of sustainable pace calculation and comparison. The interface stays out of my way, which I appreciate. It would be a five if not for depends on anthropic usage endpoint staying consistent. Recommending it to people in a similar spot.

6/11/2026 12 found this helpful
K
Kayode Silva

Decent with some rough edges

Started using Maxx casually, now it is pinned in my dock. What stands out is how it handles real time token balance in terminal status line. It just works, day after day, without surprises. Mostly using it for pacing claude code usage across a work week. The catch is depends on anthropic usage endpoint staying consistent.

4/30/2026 12 found this helpful
A
Anders Zhou Verified

Quietly excellent

Maxx has quietly become part of my daily flow. It just works, day after day, without surprises. Recommending it to people in a similar spot.

5/9/2026 11 found this helpful
A
Avery Nair

Recommended without reservation

Found Maxx on a Show HN thread and I am glad I clicked. The sustainable pace calculation and comparison is more useful than I expected. Mostly using it for monitoring token burn during intensive coding sessions.

7/17/2026 7 found this helpful