我们正在为所有 Codex 和 ChatGPT Work 付费用户重置使用量。 请继续阅读，了解 Codex 使用限制的最新情况。团队一直夜以继日地工作，审阅了数千份报告并发布修复。 根据你使用 Codex 的方式，你的使用量上限应该会比之前提高 10% 到 50%。 我们确实进行了非常细致的排查，发现并修复了许多长期存在的小问题，以下是具体情况： - 压缩。我们在压缩过程中保留了旧图像，有时会使上下文变得足够大，从而再次触发压缩。修复后，对于大量使用图像的用户，使用量下降了约 10%。已修复。 - 记忆。后台记忆工作进程可能会继承 Stop 钩子，并在该钩子不允许其完成时继续运行。这影响了不到 1% 的用户，但其中的长尾情况相当严重；我们发现有一个示例线程检查自己是否可以停止了 15,000 次。已修复。 - 目标。在某些情况下，设置的 /goal 可能已经完成，却继续超出预期的停止条件运行；或者模型会不断重试失效的工具而不停止。我们发现有些示例消耗了每周额度的 15% 到 70%。已修复。 - 自动化。某些自定义计划的运行频率可能高于配置值。已修复。 - 子代理。较小的模型（例如 Luna）有时会选择能力更强的辅助模型，即使没有被明确要求这样做。在负责协调的模型未运行于 /fast 模式时，它也可能请求子代理以 /fast 模式运行，情况同样如此。已修复。 - 计算机历史记录。较旧的实现可能会导致反复总结重叠的活动。在某些情况下，我们发现它每周消耗了高达每周使用量五分之一的额度。已修复。 - 滚动任务摘要。普通轮次会触发额外的后台请求。这些请求使令牌使用量增加了约 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!