6月30日 Tibo 预告发卡：Codex 用量额度将在接下来一小时内再次完全重置，我…

Codex 用量额度将在接下来一小时内再次完全重置，我们还会在你的重置银行里额外存入一张重置卡，供你在接下来的 24 小时内自己使用。
我们调查了有关 Codex 用量消耗快于预期的报告。并不存在某个单一的核心问题，而是几个较小的问题叠加影响了部分用户。
以下是我们发现并做出的改动：
- 实际用量：Auto-review 变得过于主动，另一项改动触发了更多 subagent 工作，后台建议在失败后可能重复运行或重试过于频繁。我们回滚了这些改动，并修复了建议调度、重复生成和重试行为。这应能减少不必要的后台 token 消耗，同时保留用户明确请求的工作。
- 用量报告：Auto-review 被错误地显示为 GPT‑5.4 用量，失败或被限流的请求仍被显示为 turns。现在 Auto-review 会作为单独类别显示，只有成功的请求才计入 turn 图表。被限流的请求从未被计费，只是显示有误。
- 即时缓解：我们在推出修复的同时重置了用量额度，随后在 CLI、桌面应用和用量后端发布了热修复。
- 后续预期：新的用量数据应更清晰，实际消耗应更低。历史图表可能仍会把 auto-review 显示在 GPT‑5.4 下，因为旧的 turn 数据没有被重新标记。像 /goal、subagents 和更高推理等级这类本就会执行更多工作的功能，自然仍会占用更多容量。
所有修复现已部署完成，我们还增加了更详细的监控，以便更早发现后台用量的回退问题。我们会继续密切关注结果。
感谢大家用 Codex 构建和做各种各样的东西。

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.