Starting today, there will be one clear improvement each day for most of all Codex or Work users. On days without one, everyone gets a full reset instead and sometimes we get both.
We’ll keep this topic updated each day.
Click on any announcement to jump straight to the relevant post.
This rebroadcast of promotional tweets for end-user subscription products seems like something belonging in the “ChatGPT” forum category.
No changes to API speed, lest you need to re-run evals against the symptoms of the “optimization”?
Looks like Improvement: ChatGPT put a “full width” option in the appearance settings.
But not an improvement: that option doesn’t make the chat contents wider to 100% like a nice Tampermonkey script might, so you can see all the code: it just auto-hides the chat history sidebar.
An improvement on a bad improvement: Now turn off the auto-rich-formatting of what you type while you type as an offered option in settings, also in appearance → advanced.
I really hope the UI interactive feature can come back.
A few days ago ChatGPT was able to create interactive study blocks directly in the chat, with answer boxes, a “Submit answers” button, scores, feedback for each answer and then the next questions based on the mistakes.
For studying it was honestly much better than plain text. It made active recall feel much more natural and useful.
It would be great if this could be restored as a normal feature!!!
Many people I know will never go to Twitter, and we are offering this as a service so everyone can keep up with what’s going on. Also, it’s fun.
Codex is a developer product that can be accessed at a steep discount compared to API pricing when using a subscription.
I’m not sure I would choose to have the team update the interface instead of improving inference speed. The latter is something I cannot do myself, while interface changes can be handled with something like a Tampermonkey script.
OpenAI has changed the targeted HTML element tree, so currently I have reversion of much of the styling I’ve also had to expectedly re-tweak in the past, including width. I haven’t made personal rule-writing updates of script for over a month, and stopped sharing long ago because of expectation a Tampermonkey script could break at any push of the underlying page structure.
With the “wide” option in settings OpenAI offers, there is no actual wider content, and clipped code in an overflow surrounded by wasted space is the symptom:
It is sufficient to say the presentation is not ideal when “bubble vision” (wanting to look like iPhone texting with un-named roles) returns to break even a single line of input, with only a left flex position and no radius working in my !important CSS (but at least is not a misalignment on the right):
Appreciation of a more work-oriented UI need would be a valuable change.
One thing that is certain when planning is the daily uncertainty in the value and availability of a stable ChatGPT surface and shape to which one might be getting acclimated - an acclimation driven by marketing campaign.
Tibo’s statements are always vague and difficult to understand (as we’ve already experienced with the reset time), so I think it’s great to have a place where we can repost things like this and discuss them
I welcome the increase to 150%
Auto-review is now free for everyone signed in with a ChatGPT account. You can enable it under Settings → Permissions → Auto-review.
For longer tasks, approving every action quickly becomes tiring unless you have spent time configuring individual rules. Auto-review adds a second agent that reviews the primary agent’s actions for you.
Its job is limited to stopping high-risk actions and anything that does not match your original request. It also does not count against your plan usage.
Sharing a friendly twist on Tibo’s 28-day challenge
What if resets became a celebration of improvements, not just the fallback?
When a meaningful improvement ships for most users, celebrate it with a global usage reset—so even users with depleted quotas can explore it properly and share concrete feedback.
On days without a major improvement, offer a banked reset, to activate when it fits each user’s workflow.
The idea is to connect every improvement with an opportunity to actually experience it: the team ships, users test, and the feedback loop gets stronger.
Would this help your workflow? I’d love to hear both the benefits and the trade-offs. If the idea resonates, feel free to support or share the original post on X so the discussion is easier to find.