maxx

Keep pace with your Claude subscription. /usage says how much of the week is gone. maxx says whether you are on pace to make it, for every account you are signed into, and when a walled one frees up.

Install →  ·  See the statusline →  ·  GitHub →

The bar. It is the last line of every Claude Code session — this one is the renderer's real output for the session that wrote this page.

/maxx accounts — one row per login, and the thing no other surface tells you: when a walled account frees up.

What maxx is

One sentence: maxx keeps you on pace with your Claude subscription. "62% used" means nothing on its own. "62% used on Tuesday, twice the pace that makes the week" is a decision. maxx turns the number into that pace and puts it in the statusline, where you will see it every two seconds, and in the gate your agents hit before they fan out.

Most people running Claude Code seriously are signed into more than one account. There is no screen anywhere that shows them together — so you find out one is walled by hitting the wall, and you find out another sat idle all day by never finding out.

/maxx accounts, at the top of this page, is that screen. Local and instant — it reads the same cache the statusline does, so it works offline and needs no network round-trip.

Underneath, maxx is a counter. It reads token usage from every Claude Code session on this machine, prices each token by model, and turns that into one question with one answer: how much can this session spend right now without ending the week early?

It answers as a rate. Your burn in percent-of-week per hour, against the rate that spends the week exactly by its reset. When you are over, it tells you the hour you run out.

Two surfaces, same number:

• The statusline at the bottom of every Claude Code session.
• The gate, a hook that reads the same number before an agent fans out, so a swarm cannot spend the week in an hour.

The problem

Claude enforces two walls: a 5-hour session cap and a 7-day weekly cap. /usage shows you the 5-hour one clearly. The weekly one is the one that actually ends your week.

A 5-hour window refills every 5 hours. So "session 100%" reads fine six windows in a row. Spend every window to its wall and the week is gone by Wednesday, with every individual session reporting "within limits" the whole way.

Agents have it worse. A subagent cannot glance at a statusline and has no /usage. Six of them spending from one pool have no idea what the siblings already took. The gate is how they find out.

How it works

1. Count. maxx reads the token metadata in Claude Code's own session logs on this machine (never prompt content).
2. Anchor. Anthropic's own /usage figure rides in on every session, already summed over every machine and agent on your login. maxx pins the count to it. Everything is reported as a percent of the week, on that denominator, because a cache-weighted token ledger never agrees with Anthropic's billing.
3. Pace. What remains of the week ÷ the 5-hour blocks left in it = this block's share. What this block has spent, on the same denominator, sits beside it. Two numbers, one denominator, compare directly.
4. Verdict. Burn rate vs. sustainable rate. Over means the week ends early, and maxx says when.

# the whole model, in three lines
block_share_pct  = week_remaining_pct ÷ blocks_left_week      # what THIS 5h block may spend
block_used_pct   = spent this block, as % of week            # what it HAS spent, same denominator
on_pace          = block_used_pct ≤ block_share_pct           # going past borrows from later blocks

Going past your share is allowed. It borrows from later blocks and breaches nothing. Burning above sustainable_pct_per_hour is the thing that ends the week early.

Install (humans)

One line. It installs the statusline, the gate and the /maxx skill. It claims nothing and calls nobody.

Restart Claude Code and the bar is there. Requires Node 18+.

Update by running the same line again.

Or install it as a Claude Code plugin:

/plugin marketplace add reif-y/Maxx
/plugin install maxx
/maxx wire

A plugin can place skills but cannot write to settings.json, so /plugin install alone gives you the commands with no statusline and no hooks. /maxx wire adds them. Run /maxx without it and the card tells you what is missing.

The statusline

One line at the bottom of every Claude Code session. Numbers lead, identity trails.

Real output of the renderer, not a mockup — the spans above are converted from the actual ANSI it emits. Colors are plain ANSI and work in any terminal Claude Code does.

/maxx commands

Local by default

The install claims nothing and calls nobody. Your numbers come from Anthropic itself: the 5-hour and weekly percentages ride in on every session, already summed across every machine and every agent on that login. maxx reads them, prices the local ledger against them, and draws the bar. No account, no network, nothing to be down.

That is also why there is no "collate my machines" step — Anthropic's number is the collation. Measured on a two-account box: the optional tally returned 83.0%/17.0%, byte-identical to what the local session already had, because it anchors to that same number.

Privacy

Nothing leaves your machine. maxx reads token counts, timestamps and model names from Claude Code's own logs. Never a prompt, never a message, never your code. It never reads them, so it cannot leak them.

Source

MIT. github.com/reif-y/Maxx

• maxx/render.mjs draws the statusline. fenix/state.mjs keeps the thread of a chat on disk so a rollover loses nothing.
• maxx/gate.mjs is the hook that reads the pace before an agent fans out.
• server/ is an optional tally for people who want one page across several machines. Nothing above needs it.

$ npm test    # node --test maxx/*.test.mjs fenix/*.test.mjs server/*.test.mjs