I’ve definitely experienced step jumps down in quality on an almost daily basis. I usually used xhigh. The experience of relying on codex’s outstandingly thorough coding earlier in the year has evaporated for me. I’m seeing incredibly stupid implementations intermittently, and have simply switched to Claude until openai takes the issue seriously. As far as i could tell they haven’t taken it seriously for the several…
I have noticed this degradation of 5.5 reliability to what, in my experience, I consider Claude-level of reliability since early June. My journey dealing with this has been transitioning from 5.5 high to 5.5 xhigh to 5.4 high. 5.4 high has been perfectly reliable for me for the last 3 weeks, and I am happy there. Occasionally, I run some tasks on 5.5 xhigh to check if it has gone back to being 100% perfectly reliable…
GPT-5.5 Codex reasoning-token clustering may be leading to degraded performance
111–120 of 165 posts
Re: GPT-5.5 Codex reasoning-token clustering may be leading to degraded performance
#112Does this affect the Codex app too, or just the Codex CLI tool?
From some of the numbers I'm seeing in the GitHub issue, the codex desktop app has the same 516 spikes. So most likely it is affected.
Re: GPT-5.5 Codex reasoning-token clustering may be leading to degraded performance
#113Earlier quoted context omitted.
Doesn't look like it: https://marginlab.ai/trackers/codex/
Thanks for sharing this project. Maybe I'm being subjective.
Re: GPT-5.5 Codex reasoning-token clustering may be leading to degraded performance
#114Earlier quoted context omitted.
I've switched 3 months ago to Codex because Claude got incredibly stupid. 6 months ago vice versa. It doesn't matter if you use Codex or Claude. Both will fuck with you at some point. Though Codex probably less.
At least OpenAI lets me use my own harness. Having to rely on insane PMs letting Claude Mythos go wild on the codebase has not been going well lately.
Re: GPT-5.5 Codex reasoning-token clustering may be leading to degraded performance
#115Deja Vu... This looks just like the Claude Code performance regression back in April. I just quit my Claude subscription when that happened and went to Codex. Now I'm kinda thinking of trying per token for both, using GLM 5.2 on Fireworks for most tasks, shelling out to the big boys only when needed. Not totally confident I'll break even though.
Re per token, I had the same reaction, but given both labs are economically advantaged moving customers to per-token consumption... almost want to avoid this on principle. Even if not intentional, benefitting from a degraded product is not something I want to accept or enable. More now than ever (since original ChatGPT release), the OSS models and open harnesses (eg Pi) are looking mighty attractive.
Re: GPT-5.5 Codex reasoning-token clustering may be leading to degraded performance
#116Earlier quoted context omitted.
But in that case you have nobody but yourself to blame, and you can stabilize things yourself at any time by refraining from making any changes. You won't be surprised by a provider. Honestly? That's not just valuable—it's essential.
> Honestly? That's not just valuable—it's essential. I'm curious if you wrote this or had a LLM write it. I'm genuinely curious to be clear as I don't see why anyone would bother to go through a LLM to write such a short reply. Have we reached the point where Claudeisms that are this obnoxious have become part of regular speech?
Re: GPT-5.5 Codex reasoning-token clustering may be leading to degraded performance
#117Earlier quoted context omitted.
I’ve always loved em dashes…very sad they’re a hallmark of LLM slop now. That and trios in arguments. Maybe I’m part LLM?
This isn’t just em-dashes—it's the empty phrase that includes both whatever the contrastive construction is called and an “Honestly”. It might have been human written but the density of LLM flags is undeniable.
Didn't the foundries take action against those in the past? I don't see "delve" nearly as often anymore. Why are the models spiraling like this now?
What really grinds my gears is the constant need to guess what I'm doing and offer a million random follow-ups. I asked what the weather was like, I don't appreciate the 5 paragraphs of tokens burned on weather-appropriate activity suggestions.
Re: GPT-5.5 Codex reasoning-token clustering may be leading to degraded performance
#118I swear all these ai companies are trying to rob us for more price
Re: GPT-5.5 Codex reasoning-token clustering may be leading to degraded performance
#119Earlier quoted context omitted.
You still have to worry about misconfigured local models. Even the professionals get it wrong, which is why local model performance is uneven across providers.
And to add insult to injury, some providers will ride on the good reputation of some local model, selling you a terrible quant instead. With OpenAI, at least my gpt-5.5 is the same as your gpt-5.5. You can't say that about glm for example.
Quants in popular local inference apps (Ollama, LM Studio, etc) are the worst possible quants (RTN).
Re: GPT-5.5 Codex reasoning-token clustering may be leading to degraded performance
#120this explains so much why gpt 5.5 has been so bad lately it was really puzzling why it struggled so much where when it first came out it was one shotting stuff totally amazing, i tried the prompt that will tell you if your plan is degraded: codex exec --json --skip-git-repo-check --ephemeral -s read-only --disable memories -m gpt-5.5 -c model_reasoning_effort=high "Do not use external tools. A black bag contains cand…