我们正在为 Codex 和 ChatGPT Work 的所有付费用户重置用量。 关于 Codex 用量限制，请继续往下看。团队这几天连轴转，翻完了上千份反馈，陆续发布了修复。 按你的使用方式不同，你应该会感觉到用量比以前多撑 10% 到 50%。 我们真的是拿篦子一寸寸梳过来的，挖出不少由来已久的小问题，以下是我们发现并修好的： - 压缩。压缩时我们保留了旧图片，有时会让上下文大到再次触发压缩。修复后，重度使用图片的用户用量下降了约 10%。已修复。 - 记忆。后台记忆 worker 可能继承 Stop hook，而 hook 又不让它们结束，于是一直跑下去。受影响用户不到 1%，但长尾相当糟糕，我们见过一个线程检查了 15000 次自己能不能停。已修复。 - 目标。某些情况下，设好的 /goal 完成后还会越过预定的停止条件继续跑；或者模型不停重试坏掉的工具而不停下来。我们见过的例子会吃掉一周额度的 15% 到 70%。已修复。 - 自动化。部分自定义计划任务的执行频率可能高于配置值。已修复。 - 子 agent。较小的模型（比如 Luna）有时会在没被明确要求的情况下挑更强的助手。同理，不在 /fast 模式下运行的编排模型也可能要求子 agent 用 /fast 跑。已修复。 - 电脑历史记录。旧实现可能反复总结相互重叠的活动。某些情况下我们看到它每周吃掉多达五分之一的周用量。已修复。 - 滚动任务摘要。普通对话轮次也会触发额外的后台请求，这部分让 token 用量多了约 1%。每次都不多，但累积起来可观。我们已经关掉了这个功能。 - MCP。部分工具结果可能被编码两次。我们还发现工具说明被截断后又重新拉取。已修复。 我们也做了架构层面的改动来防止这些问题回归，万一还是发生，团队会被直接呼叫。同时我们正在做的是，在应用里直接告诉你用量花在了哪儿，省得你自己猜。 不用说，我们正在重置用量限制，祝你周六愉快！
原文 +
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!
官方直接清空用量，不需要你做任何操作。
// 上下文
- 距上一次重置 2.2 天 · 2026-08-27
- 下一次重置在 1.2 天后 · 2026-08-31
- Codex 最新记录： 2026-09-12
- 平均间隔 6.8 天 · 最长 67.7 天 · 历史上 64% 的等待比这次短