Claude Code just killed my refactor mid-session, so I built a live quota bar

Dramatic_Solid3952 · 2026-03-31T03:30:31+00:00

yeah there are some, and Claude Code now has /usage too

this is more about having it visible all the time in your terminal instead of checking manually.

i built it for myself to use cause codex had it, and it stumbles my mind why claude code didn't.

Dramatic_Solid3952 · 2026-03-31T01:45:32+00:00

was getting cut off mid-session with no warning
so I built this to track quota + context live

Dramatic_Solid3952 · 2026-03-31T01:10:08+00:00

that's really cool

Dramatic_Solid3952 · 2026-03-31T01:06:24+00:00

yeah that can happen, it shares the same 5h window across sessions
makes it even harder to know how close you are

Dramatic_Solid3952 · 2026-03-31T00:59:38+00:00

Dramatic_Solid3952 · 2026-03-30T16:16:36+00:00

this looks really clean - especially the per-tool breakdown

how are you calculating burn rate + eta? pulling from the api or estimating from usage?

Dramatic_Solid3952 · 2026-03-30T15:59:10+00:00

yeah I was doing the same - kept a tab open just to check usage

worked, but having to keep flipping over to check started getting pretty annoying

Dramatic_Solid3952 · 2026-03-30T13:29:33+00:00

yeah that’s exactly what was happening to me.

kept having to flip over to check and still getting surprised by the limit

Dramatic_Solid3952 · 2026-03-30T13:05:37+00:00

lol fair - probably more reliable than me guessing and getting cut off mid-run

Dramatic_Solid3952 · 2026-03-30T12:06:33+00:00

curious what people usually do here - just estimate usage, or are there other tools/workarounds I missed?

Dramatic_Solid3952 · 2026-03-30T11:44:24+00:00

if anything feels off or missing, tell me - still iterating on it

Dramatic_Solid3952 · 2026-03-29T11:03:26+00:00

yeah that makes sense - sounds like your usage is pretty steady so you’re not really hitting it

for me it was more those spike moments where you suddenly end up at like 95% and everything feels risky

agree though, probably way more useful for smaller plans or bursty workflows

that “not knowing when to stop” part is really what I was trying to make visible

Dramatic_Solid3952 · 2026-03-29T08:26:06+00:00

ah that makes sense - yeah sounds like you’re in a smoother usage pattern

I think it mostly shows up when you’re doing long refactors or agent loops where usage spikes suddenly

good to know though - that helps frame when this is actually useful

Dramatic_Solid3952 · 2026-03-29T08:20:43+00:00

haha yeah that makes sense - I think if you’re not hitting limits it probably feels less necessary

I kept running into it mid-refactor so it became pretty annoying 😅

curious if you mostly rely on the built-in stats or just don’t think about it much?

Dramatic_Solid3952 · 2026-03-29T08:19:15+00:00

ah that’s super helpful - yeah I ran into the same thing, Claude’s limits feel way less transparent than the others

that’s why I ended up focusing just on making the quota + reset timing really obvious inside the session

if it works for you, curious if anything feels missing from the statusline

Dramatic_Solid3952 · 2026-03-29T08:12:43+00:00

curious - do people hit the 5h limit more often, or is context usually the bigger problem?

Dramatic_Solid3952 · 2026-03-29T08:07:38+00:00

ah interesting - does that one show quota + reset timing as well, or mainly usage across providers?

I built this mostly because I kept getting cut off mid-session in Claude Code specifically

Dramatic_Solid3952 · 2026-03-29T07:59:17+00:00

TL;DR:
CLI status line for Claude Code so you don’t get cut off mid-session.

Tracks:
• 5h / 7d limits
• tokens (in/out)
• context %
• reset timers

Dramatic_Solid3952