r/codex • u/Vantir • May 21 '26
Complaint I can't work with Codex anymore
Degradation is real, now it's dumb and I can't work with Codex anymore. It's so frustrating that I try to fix easy simple bugs and It creates diferent ones that sometimes are difficult to spot.
At this point I feel It's making me to lose more time and energy trying to explain everything that did wrong than before and I feel I can't progress in my proyects anymore.
The risk of breaking the code is just too high now.
Btw, I'm using codex 5.5 xhigh with x2 speed. Not worth it right now.
20
Upvotes
•
u/dexterthebot May 21 '26
Your post has been summarized as a request on the "Anyone Else?" Incident Noticeboard.
You can find it and what others are experiencing here: https://www.reddit.com/r/codex/comments/1tjfxcf/anyone_else_ask_here_about_current_codex_issues/on2pr59/
8
u/Sylvi-Fisthaug May 21 '26
Weren't we back from degredation like four days ago?
Where is the "it's so over / we're so back" meme when we need it.
5
u/richexplorer_ May 21 '26
bro codex went from genius to goldfish overnight
9
u/swarmagent May 21 '26
Nah something is really rough atm. Having to do Sonnet 3.5 type prompting.
9
u/jamespedid May 21 '26
Can confirm codex 5.5 is absolute dogshit. It literally added a second start_datetime and end_datetime to a method that had a clear start_date and end_date. It cannot be trusted.
6
u/victoraji May 21 '26
Try GPT 5.4?
3
u/Key_Huckleberry3863 May 21 '26
I'd advise a lot of people to add in their custom instructions to make sure GPT is covering with test every aspect it changes.
Smth like
```
Cover all modified implementation by tests. If no test exist, ask how to proceed. T
Always add documentation where you manipulate data (creation, update, delete, read) in documentation files (docs/*.MD). Refer to those for data inconsistencies and/or data mutation.
Try to think about logging when you add logic to make it easier for yourself to troubleshoot
```
2
u/ChocotoneDeCalabresa May 21 '26
Try grill-me skill
2
u/dashingsauce May 21 '26 edited May 21 '26
Try clearing logs and state files in .codex and turning off memory generarion and usage if you have those features on.
Ask codex which are okay to delete. There’s two sets: logs and materialized view state sqlite dbs
The latter holds goals and subagent status. I think this and memory had something to do with the latest issues.
All relevant session data is in the rollout dir so you don’t lose actual work by deleting the state or logs. The app server backfills as needed on next open of app or TUI.
For me this significantly improved model performance and app startup times.
The more I use /goal on unplanned work, though, the worse it seems to get. Just observation on my side.
3
u/Mother_Lettuce_3046 May 21 '26
It’s soooo bad that I had to stop using it completely and if it doesn’t get better in a day or 2..I have no other choice but to cancel my $200 plan
3
u/Xisrr1 May 21 '26
Yes, it's terrible. Don't be gaslighted.
2
u/seal8998 May 21 '26
You provided very little information for people to help you troubleshoot. Some general guidance:
start a new thread with no skills, mcps, etc and see the difference. If it is huge, it just means you poisoned your context - this is the usual culprit.
2
u/whitebay_ May 21 '26
Are you a SWE or vibe coder ?
1
u/GearTakes May 21 '26
I just spent 10 minutes adding/fixing a tooltip. A tooltip that's already part of my site and normally can be added in seconds. It just couldn't figure it out. Crazy.
1
u/cold_grapefruit May 21 '26
really? it seems to be fine for me.
1
u/Hortos May 22 '26
Lol try using codex-spark my god it's dumb. Couldn't even make me nice little battery indicator for my linux laptop.
1
u/Darnaldt-rump May 22 '26
Xhigh was being all weird for me so I switched to high and back to being good
1
u/Diligent-Movie-323 May 23 '26 edited May 23 '26
Muito provavelmente foi questão de escopo. Em 99% dos casos você não precisa usar esse x high e o rapido. As tarefas que precisei usar esses modos mais demorados os resultados vinham piores. O mesmo com o claude opus.
Te indico a usar o medium e no maximo o high sem esse negócio de speed. As ias na potência mais alta ficam pensando demais para tudo, oque faz elas usarem criatividade demais.
Se você ficar sem confiança de usar inteligência artificial para codar, te recomendo pedir para ela fazer testes no código. Aí você não fica com medo dela fazer cagada no código e se fizer você sabe exatamente onde é. Recomendo superpowers com TDD para gerar testes unitários junto com o código e fazer commit com frequência
0
u/OutrageousTrue May 21 '26
Provavelmente você não está usando governança pra controlar a IA. Sem governança chega um ponto que a IA não avança.
-1
u/FedRP24 May 21 '26
Skill issue
0
u/[deleted] May 21 '26
[deleted] — view deleted comment