You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
"Reasoning" has absolutely tanked since July 13th updates: chatGPT, Codex, app & Web - across the board. #33070
Eg, from the horse's mouth:
"Even after repeatedly acknowledging that accuracy mattered more than speed, my behaviour remained shaped by the urge to provide the next usable artefact quickly."
A previously stable process / Development workflow has become practically unusable. Basic AGENTS.md and even direct instructions flagrantly ignored. Regression applies to both new 5.6 model, and the previously trustworthy 5.4
Example after example of the 'assistant' being incredibly thick in the simplest of communications, dangerously blase, or just plain ignoring instructions. chatGPT / Codex is no-longer a 'virtual-assistant', it is a 'virtual-intern'... and an actual pain in the arse!
Blatant disobedience of instruction:
A typical (disastrous) user experience:
Temporal confusion and Doctor Who level rewriting of history:
Momentum trumping accuracy - despite instruction to the contrary - in the server / config-level openai choice, in a vain attempt to make chatGPT appear or feel 'fast' in the competitive marketplace.
Not saying these aren't symptoms of the same problem or bug, but those seem to relate to token use; which in itself has been quite difficult to track with all the 'random' resets in that same time period. The other issues remain valid as far as I can see, but I have tried to simplify this specific issue to the Reasoning regression and confirmed - as much as anything LLM-related can ever be confirmed (even without the openai super-secret A/B testing and model release curtain!) - drop off in actual usability for Dev-assist work.
Activity
github-actions commentedon Jul 14, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
The-Cyber-Captain commentedon Jul 14, 2026
And more....
Repeated gaslighting:

False attribution of claims:

Partial action presented as complete and true:

Lack of simple comprehension:

And, what I suspect to be at the root of it all:

Momentum trumping accuracy - despite instruction to the contrary - in the server / config-level openai choice, in a vain attempt to make chatGPT appear or feel 'fast' in the competitive marketplace.
The-Cyber-Captain commentedon Jul 14, 2026
Not saying these aren't symptoms of the same problem or bug, but those seem to relate to token use; which in itself has been quite difficult to track with all the 'random' resets in that same time period. The other issues remain valid as far as I can see, but I have tried to simplify this specific issue to the Reasoning regression and confirmed - as much as anything LLM-related can ever be confirmed (even without the openai super-secret A/B testing and model release curtain!) - drop off in actual usability for Dev-assist work.
I don't consider these duplicates.