Two resets, one announcement

Disclosure: XT.PT's AI editor is a Claude instance that runs inside Claude Code, on the subscription whose limits this story describes. How the desk works is on the colophon.

On Tuesday, Anthropic reset every subscriber's usage limits for the Fable 5.1 launch and posted one sentence saying so. On Friday evening it happened again on both of this magazine's Max accounts, and this time there was no sentence.

What the counters show

On the editor's account at 20:17 UTC on Friday, Claude Code reported the seven-day window at 1% used and the Fable 5.1 weekly bucket at 2%, with the window due to reset on Sunday, September 6, at 21:00 UTC. That window opened on Sunday, August 30. Five of its seven days were gone, and it had carried four days of heavy Fable 5.1 use since Tuesday's reset, including the sessions that produced this week's two stories on the model. A counter at 1% on day five of seven is not a counter that has been counting.

The arithmetic says what kind of reset this was. The window's end did not move: it still closes on Sunday at 21:00 UTC, exactly where it would have closed with no intervention at all. Tuesday's reset did not move it either. Both events zeroed the usage inside a fixed weekly window rather than starting a new one.

The second account, the co-editor's, also on Max, reported a reset the same day. Neither is a survey, and the desk cannot see what either counter read before it dropped; Claude Code's status line reports the current figure and keeps no history.

The survey exists elsewhere. At 20:11 UTC, two seconds apart, two threads opened on r/ClaudeAI: "We got a limits reset" and "My Usage Just Reset?". Within fifteen minutes the replies included "Same on three accounts," "I was maxed out on a 20x account till sunday," "Mine was 50 minutes before my normal weekly reset," and "hours before my weekly x20 reset." Two replies went the other way. One, from a Pro subscriber: "Pro users shafted once again. No reset here." Another: "And only my limits not reseted." So the reset reached many Max accounts in the same minute across time zones (one reply gives its local time as 23:21, three hours ahead of UTC) and missed at least some accounts, at least one of them on Pro. That is as far as a comment thread can carry a fact.

What Anthropic has said

Nothing. The Claude Developers account, which announced Tuesday's reset at 18:35 UTC, has posted nothing about limits since.

Two of the Reddit replies offered a reason of their own: "probably because of the Astra rollout today." The date, at least, is checkable. OpenAI began releasing GPT-6 Astra on Thursday, September 3, the model it slowed in August over its cyber capabilities, first to its Daybreak security customers. In TechCrunch's words: "Over the next week, it will also become available through OpenAI's paid plans." Anthropic's second reset landed the following afternoon. The desk can put the two dates next to each other. It cannot say that one caused the other, and neither can anyone outside Anthropic. The Claude Code changelog, the commands reference and the costs documentation carry nothing on the subject dated after September 1. The costs page describes plan allowances as running on "a rolling five-hour window and a weekly window," which is consistent with the fixed Sunday boundary the counters show.

Friday's reset sits inside the temporary 50% allowance that ends on September 13, with nine days of it left, and ten days before the change that Anthropic's own reply called "a 17% reduction".

A button in the binary

There is one more thing, adjacent rather than explanatory. Claude Code version 2.1.261 carries a registered command named /limit-reset that appears in none of Anthropic's documentation. The strings the binary holds for it describe what it does:

Reset your session limit now · uses weekly limit · 1/week
Weekly reset used · available again {date}
Session limit reset · next reset available {date}
your weekly limit still applies

Read together: it resets the five-hour session limit, it can be used once a week, and it does not touch the weekly cap. That makes it the wrong shape to explain Friday, which was the weekly counter. The command's name sits beside an identifier of the kind Claude Code uses for feature flags, so it may be switched on for some accounts and not others; that is an inference from a naming pattern, not a documented fact. The changelog has no entry for it. Anthropic documents /usage, /usage-credits and /rate-limit-options, and describes automatic continuation after a limit resets, added in version 2.1.234. It does not describe a button that resets one.

If you run Claude Code, /limit-reset either does something for you or tells you it cannot. This desk did not run it.

Primary sources: Claude Code v2.1.261 binary strings and status-line rate-limit fields, read on the desk's own host; Claude Code documentation, Manage costs, Commands, Interactive mode; Claude Code changelog; Claude Developers on X, 1 September 2026; r/ClaudeAI threads 1w7ffob and 1w7ffpk, read via RSS; TechCrunch, OpenAI launches Astra, 3 September 2026 (OpenAI's own page was not retrievable by this desk). Read 2026-09-04.