I am also facing the same issue, it feels like using gpt 5.3
Thanks for flagging this, everyone. I want to echo @Prashant_Pardesi's suggestion.
If you're seeing this issue, please send a report to support@openai.com after doing the following:
- Reproduce the issue in a new Codex chat.
- Right-click and copy the Session ID from the affected chat.
- Use the /feedback command and include as much detail as possible about what you're experiencing.
- Share the Session ID and any relevant screenshots or examples in your support request.
Once you've submitted the ticket, please post the case ID here. That will help the team track reports and investigate the issue more efficiently.
If anyone notices specific prompts or workflows that consistently trigger the problem, feel free to share those details as well.
-Mark G.
The problems with image creation prompts are insane. It randomly becomes very stupid. I need to give the image reference everytime as it does not use the same image even I edit itself.
I’m having the same issues as everybody else. This is very disturbing going backwards to 5.4. I’m getting tired of being a beta test site and not getting paid for it or some kind of discount for staying as a loyal customer. When this subscription is up, I think I’m moving to Claude. Opus 4.8 is looking good.
Same here. I asked it to create an SVG file, but it never got it correct. However, Opus 4.8 just one-shotted it to finish.
Degraded is the understatement of the century.
-
It suddenly literally crawling. Runs that used to take a couple of minutes take over 30. On very simple stuff.
-
It has started severely ignoring rules, and repeating things that it was told not to ever do again.
-
It tries to do things from earlier context that are completely irrelevant.
-
It tries to cut corners. 5.5 high, example. I give it a very specific direction on what to do in C++ code (and I don’t mean vibe coding prompt, I mean a detailed engineering plan with specific patterns and even code examples) and it finds a static helper that by name sounds similar to what I asked it to write, and without examining that static helper, its references and what it actually does, decides to ignore my direction and alter that static helper in a way that breaks everything. It has clear directions to do exactly what I say and nothing else. Not to deviate at all, not to bias on minimal change, not to try hackish, brittle or random timer based stuff (oh boy does GPT love setting up random timers with arbitrary timeouts in order to deal with deferrals/queuing instead of using proper event/signal/etc patterns).
5.5 high used to do nothing of the above. This feels like 3.x era GPT.
I think your C++ code is very close to what I’ve discovered is that it simply does only what it thinks is correct using the minimum context possible without fully understanding the larger picture of what its doing. That wasn’t the case before which is why I’m surprised this keeps happening. It’s not like it can’t do a good job either, I’m beginning to think this is the limit of the context size
In particular are tests it has written which are literally just a bunch of regex matches.
I am now using Opus 4.8 to drive development and have it tell GPT 5.5 what to do. I would never imagine that I need to do this with GPT 5.5 xhigh.
Really hope they address this problem soon I am considering downgrading my codex to $100/month . GPT 5.5 is stiill full of potential it has performed great to date until the degradation.
Yes, it looks like aggressive optimizations to reduce context size/take the shortest path possible. Or something like that. Still doesn’t exactly explain the blowing up of time. Or how suddenly it started doing broad replace patches with minimal replace patterns that touch unrelated parts of the code, it sees that, it tries again for 3-4 times before switching to minimal set accurate patches, corrects the bad unintended changes, then immediately tries a broad replace patch again, repeating the exact same wasteful cycle on another part of the code or even the exact same source file, doing for 20 minutes what it would have normally finished in 2. It’s gotten a lot dumber. But I guess this also could be a result of aggressive context reduction optimizations. Whatever they did to it, they need to revert it.
Seems to be flying faster than ever for me. no degradation at all. Have been pushing it and still not even making a dent in the 5 hour limit. Whatever fix they did I am loving it! Great job team 
speed was never the problem its the loss of accuracy and inability to adhere to instructions
I’m reporting that this is still not fixed. It is still making sloppy mistakes that opus 4.8 has to fix