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 · @SimonasLTU1 This was all client-side + network for playground only. Shipped optimized rendering logic that can keep up with ultrafast, try again
Okay, so as a poor peasant with a ChatGPT Pro $100 subscription and like $2 sitting in my OpenAI Playground balance, I decided to test GPT-6.1 Sol ULTRAMOTHERFUCKINGFAST in the API.
The result?
12,566 output tokens in 4 minutes 16 seconds.
Do the math 😂 That's about 49 tok/s.
I don't know... maybe I'll try it one more time to see if that's actually the real speed, but if it is, I'm sorry, calling 49 tok/s "Ultrafast" is pretty horrible...
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.
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