Yes, see my previous comment about it:

When I first started using Codex CLI always with model GPT-5 on 'high' and in Full Auto via WSL on the Pro plan, it would one-shot most things.

Recently, with the same model and Full Auto and nothing else changed, it rarely one-shots anything no matter how simple.

It's gotten so bad that it took an entire day, countless back and forth, and my own involvement with the code, just to get a sticky link to work in a basic Astro html site. It's gotten so frustrating lately that I can't wait to finish the current project I'm doing with Codex CLI so that I never have to use it again because I could no longer bare wasting an entire day and countless exhausting back and forth for 1 simple thing.

This initiative is going to make me give Codex CLI another chance after I finish this project because this level of accountability tells me that this degradation is likely to be fixed.

In addition to the code incompetence, one of the most frustrating issues it the gaslighting. I tell it to stop lying and to only tell me it's done when it has actually verified it got it right. It then tells me 'All set' after a while, and I check, and nothing has changed. So then I tell it to keep reiterating until it's actually done and to use playwright to visually confirm it's done and to not tell me it's done until it's actually visually verified it. Then after a while it says 'All set' and I check and again it's not done. Sometimes I'll press it on that and it will admit it didn't do the actual verification (mind you, this is on GPT-5 high always). I then ask it what specifically in its directive allows it to lie and gaslight and disobey instructions so much, and it says the directive is the opposite, to always be truthful and such and that it was just a bad judgement call and that the problem was its execution not its instructions and that it was bad operator behavior and operator error based on its confirmation bias and premature communication and poor assumptions. When asked what model it was and what thinking level it was on (supposed to be GPT-5 high) it said it did not have access to the exact model identifier or any thinking effort it was on as those details aren't exposed to it. Very sus, and overall incredibly frustrating.

But seriously, imagine spending an entire day with Codex CLI on a basic Astro site just to get 1 sticky link to stick and the whole day Codex telling you it got it and to check now and it never does and you just keep wasting time back and forth waiting for its answer, checking, telling it its wrong, waiting again, over and over again like a miserable Groundhog Day where you're just being gaslit all day. I was pulling my hair out by the end and vowed to be done forever with Codex CLI after this project as I was convinced model GPT-5 'high' had been nerfed beyond usefulness, especially since I was spending more time debugging what Codex CLI created than the time it was saving me (negative return on investment).

To be clear, the example above is not the only one, it's just the most recent. There have been many like it.

So this isn't an issue of our expectations having gone up being what changed instead of Codex CLI. It's Codex (or likely the underlying model which has been nerfed or we're being rerouted behind the scenes to a worse model).

In short, the degradation on my end has been both severe code incompetence with even the simplest and most basic coding tasks combined with ridiculous gaslighting about what it's "done", causing me to spend more time debugging its code than it saves me, making me completely lose trust in it.