这是一场常规公开重置事件。原公告决定哪些账户被覆盖，以及它是否自动生效。
官方公告原文：「We are reseting usage for all paid users of Codex and ChatGPT Work. Please conti…」
公告细读：390 个单词的公告属于典型事故通告结构——说明状况、确认修复、宣布补偿。这类公告在「三月事故期」之后逐渐形成了固定句式。
事实快照QUICK FACTS
| 项目 | 数据 |
|---|---|
| 公告时间 | 2026-08-29 20:43 UTC（北京时间 2026-08-30 04:43，周日） |
| 类型 | 全员额度重置（reset_type: regular） |
| 历史排位 | 第 48 场 / 共 70 场 |
| 距上一场 | 2 天 |
| 距下一场 | 1 天（下一场：2026-08-31） |
| 当时点的运行平均间隔 | 7.4 天（此前 46 个间隔的均值） |
| 本场间隔在历史上的位置 | 比此前 17% 的历史间隔更长（当时已记录的间隔中排第 28 长） |
| 信源 | @thsottiaux 的公开公告 ↗，由 codex-resets.com 归档 |
事件时间线TIMELINE
-
2026-08-30 04:43（北京时间）Codex 团队发布重置相关公告；覆盖范围以原文为准。
-
公告原文
“We are reseting usage for all paid users of Codex and ChatGPT Work. Please continue reading for an update on Codex usage limits. The team has been working around the clock, going through thousands of reports and shipping fixes. Depending on how you use Codex, you should see your usage go between 10% and 50% further than before. We really went with a fine comb, with many uncovered small things being longstanding and here is what we found and fixed: - Compaction. We were keeping old images during compaction, sometimes making the context large enough to trigger compaction again. After the fix, usage dropped around 10% for users making heavy use of images. Fixed. - Memory. Background memory workers could inherit Stop hooks and keep running when the hook wouldn’t let them finish. This affected fewer than 1% of users, with the long tail being pretty bad and we saw one example thread check whether it could stop 15,000 times. Fixed. - Goals. In some cases, a set /goal could finish and then keep going past the intended stop condition, or the model would keep retrying broken tools without stopping. We saw examples consume anywhere from 15% to 70% of a weekly allowance. Fixed. - Automations. Some custom schedules could run more frequently than configured. Fixed. - Subagents. Smaller models (e.g. Luna) sometimes picked more capable helpers without being explicitly asked. The same was true where the orchestrating model not running in /fast mode could request sub-agents to run /fast. Fixed. - Computer History. The older implementation could lead to repeatedly summarizing overlapping activity. For some cases we saw it consume up to one fifth of the weekly usage per week. Fixed. - Rolling task summaries. Ordinary turns were triggering extra background requests. These added about 1% to token usage. Small each time, but it adds up. We have disabled this. - MCP. Some tool results could be encoded twice. We also found tool instructions getting cut off and fetched again. Fixed. We’ve also made architectural changes to prevent these from regressing and our teams will get paged if it happens regardless. We are also working on showing you directly in the app where your usage goes so you don’t have to guess. Goes without saying that we’re resetting usage limits and I hope you enjoy a very nice Saturday!”— @thsottiaux on X ↗（英文原文）
-
生效事件按公告写明的范围生效；请在账户 Usage 页面验证。
本场所处的时期：里程碑与重置券ERA CONTEXT
这一段档案记录了 2000 万、2500 万用户里程碑、8 月 21 日的重置券发放，以及月末的多场庆祝事件。记录本身不足以证明未来发布节奏或官方意图。
在完整序列里，本场是「里程碑与重置券」的第 5 场（该时期共 6 场）；1 天之后，下一场重置在 2026-08-31 如期落地。周六官宣、间隔 2 天，这些数字放在一起，就是本场在整条时间线上的坐标。
这对你意味着什么WHAT IT MEANS
常规事件的历史间隔波动很大；间隔只能描述过去，适用范围与到账方式必须回到原公告和 Usage 页面。本场间隔极短，属于典型的连发节奏——在这类时期里烧额度，被回血补上的概率是全档案最高的。
常见问题FAQ
2026年8月29日（周六）的 Codex 重置事件是什么？
2026年8月29日（周六），Codex 团队发布了一次全员额度重置相关公告——这是档案中的第 48 场（共 70 场），距上一场 2 天，归属于「里程碑与重置券」。原公告检测到范围：all_paid / work；是否覆盖你的账户以及是否需操作，以原公告与 Usage 页面为准。
距上一场才 2 天，连续重置正常吗？
正常。档案中多次出现连续重置（本场所属的「里程碑与重置券」就集中了 6 场事件），通常与用户里程碑、发布周或事故收尾相关。连续重置期恰恰是「猛猛蹬」建议出现最多的时段。
这场之后，下一次全员重置是什么时候？
档案里有确切的历史答案：下一场记录在 1 天后的 2026-08-31。这是事后档案，不是当时可以获得的预测。