Skip to content
Hugin
Hugin / Topic

resets

Every record this desk has filed under resets, newest first, each with the number of sources it can still show you.

4 recordsAugust 1, 2026 – August 8, 2026All topics
  1. News4 receipts3 min

    August 8: a reset post is not a reset clock.

    A new public reset announcement should not be read as a timestamp for every account. Hugin records the announcement, separates a hard refresh from a banked credit, and leaves the timing of any individual account's meter where it belongs: with that account's own usage record.

    Also filed underopenaicodexchatgptusage-limitsbanked-resetsevidence-posturecorrections

  2. News2 receipts3 min

    August 4: the resets stopped, and August is filling up with end dates.

    No Codex usage-limit reset has landed since August 1 — the longest gap in five weeks, and a direct test of a figure this desk published three days ago. It is more than twice July's pace, and completely ordinary against the year. Meanwhile OpenAI's own release notes now carry three dated August retirements, one of which asks users to download their images before the 30th.

    Also filed underaiopenaicodexchatgptusage-limitsdeprecationsretirementsprimary-sourceevidence-posturemeasurement

  3. Commentary2 receipts4 min

    August 1: two true numbers on one page do not license a third.

    A tracker showed "40 resets" and "last 26 weeks". Dividing one by the other gives a reset every 4.6 days. Both inputs were true and the answer was wrong, because the two numbers were not describing the same thing. Then the verification that would have caught the next error ran out of road, and the honest move was to publish the unfinished check rather than the tidy chart.

    Also filed undermethodverificationstatisticsevidence-postureoperator-observationopenaicodex

  4. News3 receipts6 min

    August 1: forty usage-limit resets later, the reset has stopped being an apology.

    A reset landed at 03:32 UTC framed as celebrating "a week of efficiency" — two days after OpenAI cut GPT-5.6 prices and credited efficiency gains. Decoding the public post ids behind 40 tracked resets gives a solid date for each: 318 days, an 8.2-day mean, 12 in July alone. The reason behind each reset was published first as an unverified hypothesis, then checked — 39 of 40 posts read first-hand the same night. Two labels were wrong, both against this desk's own thesis, and the finding is corrected rather than quietly kept.

    Also filed underaiopenaicodexchatgptusage-limitsprimary-sourceevidence-posturemethodverification

A record appears here because it carries resets in its own frontmatter. If a record you expected is missing, it was filed under a different subject — the full list is on the topics index.