Codex is rapidly degrading — please take this seriously

div I’ve been using **Codex in the web version since the very first day of its release**, and I can confidently say that **until around mid-September it was an outstanding tool**. After the release of what seems to be the **GPT-5-Codex** update, things have gone downhill fast. … - Codex **no longer completes tasks reliably** — in roughly **two-thirds of all cases**, tasks either hang indefinitely or end with *“I could not do this task.”* - It **makes a huge number of mistakes and regressions**, even in simple, previously stable workflows. - **The new “code review” feature**, which is supposed to help, now actually highlights how bad things have become — it finds **bugs and logical inconsistencies in almost every piece of code generated by Codex itself**, forcing me to **rerun and re-fix the same task over and over**. - Because of this, **two-thirds to three-quarters of all consumed limits go not into building, but into cleaning up Codex’s own mistakes** — and that’s on top of the fact that **the new usage limits no longer allow running tasks at the same pace and volume as before.** - Front-end generation has become absurd — it **ignores provided designs** and outputs something completely unrelated. To give some context — in **August**, I wrote over **300 000 lines of solid code** with Codex. Now, more than a month later, I **can’t even isolate one persistent bug**, and I’m unable to render a mobile UI without launching separate tasks **for every single component**. Honestly, the best decision right now would be to **roll everything back to the late-August state** and rebuild from there. Because right now, **you’re losing developers who were genuinely invested in this tool** — when **the GPT-5 model embedded in third-party agents performs better than OpenAI’s own core Codex service**, that’s a serious signal that something is fundamentally broken. … Long-running sessions are meaningless when after 1–2–3 hours of continuous work **there’s no guarantee the code isn’t riddled with hidden bugs.** Because of that, we’re forced to **overcomplicate our prompts** — making Codex re-check and re-verify its own output multiple times, trace affected code paths, and cross-check logic. That in turn **overloads your servers even more.** And with the constant **task freezes and “I couldn’t do this task” messages**, we end up running **the same job 4, 8, or even 12 times in parallel** just to get one usable result. So yes — technically Codex can “run for 6 hours,” but practically, **it can’t finish a 6-minute job reliably anymore**. … These days, even tweaking one CSS rule can hang for 15 minutes, so I end up force-quitting it… I was loving it - but I am ready to look for other options at this point. I have to ask it 3x to fix a simple thing, then when even CODEX realizes it keeps attempting the same fix, it says I give up.. I cant do it.. and then refuses even if I give it an alternate working fix. I also have been using Codex Web since it was still fresh, and its usefulness has diminished greatly since GPT5, and especially 5.1. Refactors used to be painless, now they are painful Its in it’s infancy. I recently posted something i never thought it could do but it did. ... Codex used to work really well, but after the recent update it’s become slow, unreliable and full of mistakes. Tasks fail, the code review tool catches problems codex creates itself , and even simple UI works now takes too much time. This is slowing down my work and i just want Codex to go back to the stable version we had before. It was a great tool, and i hope it gets back to that level soon. … It has become abundantly clear to me that feedback is of no importance to the Codex and OpenAI teams; their communication with users and developers is an utter failure. Judging by the situation, either the team has lost its engineering expertise, or it is being stifled by marketers.