@testingcatalog· @testingcatalog · X·· 2026-08-30精选AI 评分67
AI 导读
OpenAI 再次为 Codex 和 ChatGPT Work 的全部付费用户重置用量额度,并修复多项用量消耗问题,用户整体可用量比此前多出 10% 到 50%。官方公布的修复包括 compaction 阶段遗留旧图片导致重复压缩、后台 memory worker 继承 Stop hooks 无法停止、set /goal 超出停止条件继续运行、自定义 automations 执行频率高于配置、子智能体未经要求调用更强模型,以及 Computer History 重复汇总重叠活动、普通回合触发额外后台请求、MCP 工具结果被重复编码等,并称已做架构调整防止回退。官方还表示正在开发在应用内直接展示用量去向的功能。
推荐理由
原文逐项列出八类用量异常的原因与修复结果,读者可据此判断 Codex 付费额度实际能多用多少。
正文
OPENAI 🔥: Codex and ChatGPT Work usage limits are being reset once again.
Besides that, OpenAI is fixing various usage consumption issues so your overall usage limit will become higher than before.
> Depending on how you use Codex, you should see your usage go between 10% and 50% further than before.
K.O. 👀
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!在 X 查看被引用的帖子
来源:@testingcatalog · x.com