Tibo@thsottiaux · 3天前43Codex usage limits will be fully reset again in the next hour and we will credit one additional reset into your bank for your own usage over the next 24 hours.
We investigated reports that Codex usage was being consumed faster than expected. There wasn't one central issue, but a few smaller problems compounded for some users.
Here's what we found and changed:
- Actual usage: Auto-review had become more proactive, another change was triggering more subagent work, and background suggestions could run twice or retry too frequently after failures. We reverted the changes and fixed suggestion scheduling, duplicate generation, and retry behavior. This should reduce unnecessary background token consumption while preserving the work users explicitly request.
- Usage reporting: Auto-review was incorrectly appearing as GPT‑5.4 usage, and failed or rate-limited requests were still shown as turns. Auto-review now appears as its own category, and only successful requests count toward the turn graphs. Rate-limited requests were never charged, but they were being displayed incorrectly.
- Immediate relief: We reset usage limits while rolling out the fixes, then shipped hotfixes across the CLI, desktop app, and usage backend.
- What to expect: New usage data should be clearer and actual consumption should be lower. Historical charts may still show auto-review under GPT‑5.4 because older turn data was not relabeled. Features that intentionally perform more work; such as /goal, subagents, and higher reasoning levels will still naturally use more capacity.
All fixes are now deployed, and we've added more detailed monitoring so we can detect background-usage regressions sooner. We'll continue watching the results closely.
Thank you for building and doing all sorts of things with Codex.
译Codex 使用限制将在下一小时完全重置,额外一次未来24小时重置。消耗过快并非单一原因,而是自动审查更主动、某些改动触发更多子Agent、后台建议重复生成或失败后重试等小问题叠加。现已回滚相关改动,修复调度、重复生成和重试行为,减少不必要的后台token消耗。使用报告方面,自动审查此前被错误归类为GPT-5.4使用量,已单独分类;仅成功请求计入轮次图表。所有修复已部署,并增加更详细监控。团队周日紧急排查日志。