The Reset Is Free. The Timing Isn't.

A free full limit reset showed up in my Claude usage settings this week. It's a nice gift, and an easy one to waste: press it too early or too close to the regular reset, and much of it is gone. Two questions came with it. How do I find out when an account gets one, without checking a web page? And if I run two accounts, is this two free weeks?

Short answers: my terminal now tells me. And both of mine got one, so almost two free weeks, provided each reset is timed.

What a reset is, and what it isn't

I covered where resets live in You'll Thank Me Later: Free Limit Resets. This one is about spending them.

Claude's Help Center page "What is a limit reset?" describes an occasional offer on eligible plans that restores usage, in three kinds: a five-hour reset, a weekly reset and a Fable limit reset. Limits are shared across the account, so a reset pressed in the browser also refills Claude Code. An unused one expires at the time on the offer.

One sentence on that page decides everything below: using a reset doesn't change your weekly limit's schedule. Weekly limits still reset on their usual day and time.

My first account shows two grants today:

• "One full limit reset (November 2026)": one left, ending December 10 at 22:00 UTC (14:00 Pacific), usable now (you don't have to be at the limit), and it clears the weekly limit for every model plus the Fable allowance.
• A Fable reset from a model launch, ending March 9, 2027 at 07:59 UTC (March 8, 23:59 Pacific). It gives back only what Fable used this week.

My second account holds the same full reset plus three Fable resets from that launch, shown as not usable right now. Check yours; I can't say what every plan received.

The timing math

Because the weekly reset day stays put, a reset is worth a full weekly allowance only if you use all of it before the regular reset would have refilled the account anyway.

So the rule has three parts: at the wall, early in the account's week, with work queued.

Two accounts, two clocks

I run two Claude accounts. My plan for a heavy stretch was simple: exhaust both weekly limits, reset both, and that's basically two free weeks.

It's close. Both got a full reset, so that's two extra weekly allowances, and in raw capacity the plan holds. In calendar time it holds only if each reset is pressed against its own account's week. Say account A resets on Tuesdays and account B on Fridays:

• A hits its wall on Thursday evening. Its regular reset is four and a half days out, so reset A and keep going.
• On Thursday, with A at its wall, don't reset B as well just because the work is heavy. B's Friday reset is a day away, so its refill would mostly go to waste.
• B hits its wall the following Monday. Its regular reset is four days out, so reset B then.

Then the expiry date caps all of it. My full reset ends December 10, so it only helps in the weeks before then. If the deadline arrives before the wall, you have to press early, which puts you back in the "early, at 74% used" row.

Knowing without checking

The other way to waste a reset is forgetting it until it expires. Settings > Usage is the official place to look, and a calendar entry is the zero-effort fallback. I wanted something I couldn't miss, in the terminal where I already work.

Claude Code already knows

Claude Code 2.1.322 carries the feature internally. When the CLI asks Anthropic's OAuth usage endpoint for usage with one extra query flag, the answer includes a block of reset grants: resets left, end date, which limits each clears, whether it's usable now, whether it's paused. The binary also contains a hidden /limit-reset command ("Which reset do you want to use?", "your weekly reset day stays…"), switched on by a server-side feature flag that was off for my accounts. That fits the Help Center: no reset button in Claude Code.

Treat this with care. The endpoint is undocumented and can change without notice.

What my harness does with it

My harness is my own layer around Claude Code: a launcher that picks the account, a statusline, and a dashboard band drawn above the prompt. Every 15 minutes, for each signed-in account, it reads the reset block with that account's existing token, held in memory only. It never claims a reset. While any account holds an unused one, the band shows a green row, one entry per account (wrapped here; times are local, this sample uses UTC):

FREE RESET  a@example.com
              full reset until Thu 10 Dec 22:00 (29d left)
              Fable reset until Tue 9 Mar 07:59 (117d left)
            b@example.com
              full reset until Thu 10 Dec 22:00 (29d left)
              3 × Fable reset until Tue 9 Mar 07:59
                (117d left) not usable now
            claude.ai/settings/usage

Which account, what each reset refills, when it ends, and where to use it. The same note sits in the account picker at launch, which is exactly when I choose which account takes the work. Once a reset is used, its line is gone on the next read, within 15 minutes; the row goes when no unused reset is left. An account the harness can't read stays listed with the reason (signed out, say); if it was read before, its last answer stays too, dated, so an old reading never passes for a fresh one.

Pressing it is still a manual call: it depends on what work is queued and how far each account is from its own reset.

Before it expires

Open Settings > Usage on each account today. Hold any reset you find until a wall lands early in that account's week, or until its deadline, whichever comes first.