额度重置 · 用量异常补偿

Codex 使用限额将在接下来一小时内再次全面重置，并且我们会额外向你的银行存入一次重置，供你在接下来 24 小时内自行使用。 我们调查了有关 Codex 用量消耗速度高于预期的报告。并不存在单一核心问题，而是一些较小问题叠加影响了部分用户。 以下是我们发现并做出的更改： - 实际用量：Auto-review 变得更主动，另一项更改触发了更多 subagent 工作，后台建议可能会运行两次，或在失败后过于频繁地重试。我们回滚了这些更改，并修复了建议调度、重复生成和重试行为。这应能减少不必要的后台 token 消耗，同时保留用户明确请求的工作。 - 用量报告：Auto-review 被错误地显示为 GPT‑5.4 用量，失败或被限流的请求仍被显示为轮次。Auto-review 现在会作为独立类别显示，只有成功的请求才会计入轮次图表。被限流的请求从未计费，但此前显示有误。 - 即时缓解：我们在推出修复期间重置了使用限额，随后在 CLI、桌面应用和用量后端发布了热修复。 - 预期情况：新的用量数据应更清晰，实际消耗应更低。历史图表可能仍会将 auto-review 显示在 GPT‑5.4 下，因为较早的轮次数据没有被重新标注。那些会有意执行更多工作的功能；例如 /goal、subagen

Codex 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.