OpenAI重置Codex与ChatGPT Work用量，修复多项计费漏洞
We are reseting usage for all paid users of Codex and ChatGPT Work.
We are reseting usage for all paid users of Codex and ChatGPT Work.
我们正在重置所有Codex和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.
请继续阅读，了解Codex使用限制的最新动态。团队一直在夜以继日地工作，处理了数千份报告并发布了修复。
Depending on how you use Codex, you should see your usage go between 10% and 50% further than before.
根据您使用Codex的方式，您应该会看到使用量比之前多出10%到50%的余地。
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.
我们确实进行了细致的排查，发现许多被忽视的小问题长期存在，以下是我们发现并修复的内容： - 压缩。我们在压缩过程中保留了旧图像，有时会使上下文大到再次触发压缩。修复后，重度使用图像的用户使用量下降了约10%。已修复。 - 内存。后台内存工作线程可能继承停止钩子，并在钩子不允许其完成时继续运行。这影响了不到1%的用户，但长尾情况相当糟糕，我们看到一个示例线程检查了15000次是否能够停止。已修复。 - 目标。在某些情况下，设置的/goal可能完成后继续超出预期的停止条件，或者模型会不断重试损坏的工具而不停止。我们看到示例消耗了每周配额的15%到70%。已修复。 - 自动化。某些自定义计划可能比配置的更频繁运行。已修复。 - 子代理。较小的模型（例如Luna）有时会在未被明确要求的情况下选择更强大的助手。同样，如果编排模型未在/fast模式下运行，也可能请求子代理以/fast模式运行。已修复。 - 计算机历史。旧实现可能导致重复总结重叠活动。在某些情况下，我们看到每周使用量高达五分之一被消耗。已修复。 - 滚动任务摘要。普通轮次触发了额外的后台请求。这些增加了约1%的令牌使用量。每次虽小，但累积起来可观。我们已禁用此功能。 - MCP。某些工具结果可能被编码两次。我们还发现工具指令被截断并重新获取。已修复。
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!
不用说，我们正在重置使用限制，希望您享受一个愉快的周六！
更进一步：量化金融体系
看懂新闻只是起点——沿量化金融路径，把它变成能交付的工程能力