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.
Hi Astra users. A reset and a quick update on quality issues that have been posted around.
Working with some of you, we have found and fixed the following issues:
- Some skills written for previous models were triggering too often or preventing the model from checking its work.
- An opt-in context management experiment that could cause early stops or replies to older messages. We've disabled it. Our rough estimate is that 4-5k users were affected by this experiment.
- We've also removed some badly configured engines that resulted in a measured quality degradation for a long tail of traffic flowing through them.
We’ve also made some more minor improvements and things should feel significantly better across the board. More consistent follow-through, better tracking of your latest message, and better checks on the work as it’s going through the motions.
The examples posted and all the users who worked directly with us were incredibly useful in helping fix things quickly. Always grateful for this incredible community.
And of course, a reset is also landing by midnight today.
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