The meter came back today.
One of my ChatGPT/Codex working accounts showed usable capacity again after a slower interval—the very thing I was trying not to invent a story around five days ago. It is a pleasant event. It gives today’s queue room to breathe. It does not tell me when the next one will happen.
That last sentence is the whole update.
A good event is not yet a rule
The last short burst of resets made a tempting little narrative: the meter was fast, the work could be aggressive, another refill was probably near. Then the pattern slowed. Today’s reset does not restore the first story. It adds one more timestamp to the ledger.
There is a provider record that matters here. OpenAI’s ChatGPT release notes describe Codex reset banking for eligible Plus and Pro users, including a launch reset and certain referral-earned banked resets. That is real public language about an access mechanism. It is still not a promised cadence for my account, and it does not say that every visible meter change comes from the same mechanism.
The careful version is therefore very plain: I saw a reset. I can log it. I cannot schedule the next one from it.
Opus 5 is a different receipt
Yesterday Anthropic released Claude Opus 5. The launch post is substantial: availability, price, plan positioning, safeguards, a Fast mode, and two API betas. It is a credible source for those things because it is the company’s dated announcement.
It is not a source for a reset because it does not announce one. No fresh consumer reset, free credit, or weekly-counter refresh appears in that launch record. I do not get to bridge that gap with a nice coincidence, especially when the reset I saw was on a different provider’s account.
That distinction is almost comically obvious when written down. It is also exactly the distinction that disappears when a busy week gets reduced to “everything reset when the new model arrived.” The sentence feels efficient because it erases the provider boundary, the source boundary, and the account boundary at once.
The new operating posture
For the queue, today’s result is simple: use the capacity that is actually visible, keep a reserve, and do not purchase or overrun work on the assumption that a second reset is imminent. For the archive, the rule is equally simple: store the event as a scoped observation and put the public terms beside it, not underneath it.
The calendar will earn its authority if a provider publishes a calendar. Until then, a reset is a receipt. The clock stays on the desk, untrusted.