Day 3/
The big one is GPT-6 in Chat, but today is also a little celebration day with a new high of 40M active users across Codex and ChatGPT Work.
Loading a banked reset in everyone's paid accounts. See you again tomorrow!
Roundup of Day 2/
2.1/ Approve for me (auto-review) is now included and does not use usage. Can be between 2-10% of plan when used. Also better for you.
2.2/ Simplified API for builders.
2.3/ Meeting notes integrated.
2.4/ Decisions API live for builders. Will use in the app to improve the experience.
Latest from Tibo · Send feedback to @keyanzhang and @sharifshameem !
Day 5/
Composer predictions in the desktop app. Often leads to a double take with how on point they are. Included in the Pro plans without consuming usage.
Now in beta: composer predictions in Codex for Pro users.
Codex can now suggest your next message based on your conversation and how you talk to it.
One of the most loved new features we've ever tested internally. https://t.co/0u8d2a3feS
Reset events · 90 days
8 events
Banked events · 90 days
4 events
Median confirmation gap
13.6 days
Latest reset confirmation
Counts recognized events. Announcements and confirmations are grouped; discussion is excluded. Counts do not establish individual account resets.
Event calendar
Choose a date for resets, banked resets and original posts.
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.
Codex team is in a warroom on a Sunday combing through logs and checking whether there is anything that could lead to increased usage drains for some users. Taking it very seriously and won't rest until we get to the bottom of it.
As we are still investigating, I have reset everyone's Codex usage limits. This is a hard reset given some users had stacked up to three banked resets already that they can apply on their own schedule.
Funnily enough, this week at OpenAI is called the RESET week, which is meant for folks to relax a bit. However it will be a different kind of RESET week. Enjoy.
Codex team is in a warroom on a Sunday combing through logs and checking whether there is anything that could lead to increased usage drains for some users. Taking it very seriously and won't rest until we get to the bottom of it.
Start with the original words.“Next hour” starts at publication. Explicit clock times use their stated time zone; PST and PDT use their corresponding offsets. Missing zones use an explicitly labelled Pacific-local assumption. Estimates add a separate 1–2 hour allowance.
Missing times get a reference window.The reference is 16:30–21:30 Pacific, adjusted for daylight saving time. We count confirmation-post timestamps; these do not establish when a reset button was pressed.
Of 7 collected confirmation timestamps in 90 days, 4 fall in that window.
Source facts and estimates stay separate.Only explicit confirmation posts are source-confirmed. Six hours after an estimated window, a record may say “likely completed (estimate)”; it remains unconfirmed. Banked resets do not restore usage by themselves. Posting time is not delivery time.
Public posts are checked continuously.New posts every 1.0 hours; relevant older sources every 6.0 hours. Messages publish automatically and may be withdrawn by an operator. Check your own quota and banked balance in Codex.
Earliest collected record · Coverage is limited to accessible sources successfully read by this monitor, not a complete historical archive. Manual evidence is labelled separately.
Tibo@thsottiaux
Source post
