reasoning_output_tokens count percent
━━━━━━━━━━━━━━━━━━━━━━━━━ ━━━━━━━ ━━━━━━━━━
0 873 28.5948
───────────────────────── ─────── ─────────
8 64 2.0963
───────────────────────── ─────── ─────────
9 60 1.9653
───────────────────────── ─────── ─────────
11 54 1.7688
───────────────────────── ─────── ─────────
516 48 1.5722
───────────────────────── ─────── ─────────
12 45 1.4740
───────────────────────── ─────── ─────────
10 43 1.4085
───────────────────────── ─────── ─────────
17 40 1.3102
───────────────────────── ─────── ─────────
13 38 1.2447
───────────────────────── ─────── ─────────
14 36 1.1792
Created a script for this: https://github.com/thehappybug/codex-reasoning-token-checkGPT-5.5 Codex reasoning-token clustering may be leading to degraded performance
151–160 of 165 posts
Re: GPT-5.5 Codex reasoning-token clustering may be leading to degraded performance
#152anthropic at least does have a latest and stable channel, as the other day they pushed something irritating that would skip question asking phase if you didn't reply in 60 seconds, and it broke my multi terminal workflow. like I don't know what their product people are thinking when they push this kind of stuff, but it made me switch to stable
Re: GPT-5.5 Codex reasoning-token clustering may be leading to degraded performance
#153Indeed, it looks like my work has suffered from the clustering issue as well: reasoning_output_tokens count percent ━━━━━━━━━━━━━━━━━━━━━━━━━ ━━━━━━━ ━━━━━━━━━ 0 873 28.5948 ───────────────────────── ─────── ───────── 8 64 2.0963 ───────────────────────── ─────── ───────── 9 60 1.9653 ───────────────────────── ─────── ───────── 11 54 1.7688 ───────────────────────── ─────── ───────── 516 48 1.5722 ───────────────────…
Some were definitely below par, and I recall having to iterate on the generated code more than I wanted to. However, it is only true for a very small number of conversations.
So we're looking at a small set of affected conversations, and even within that small set, only a few will have degraded output, likely because the model can compensate for the reasoning defect over the long conversation.
Re: GPT-5.5 Codex reasoning-token clustering may be leading to degraded performance
#154Earlier quoted context omitted.
How do you mean OpenAI lets you use your own harness? I'm under the impression that a custom harness requires the OpenAI SDK, which requires api tokens rather than plus/pro accounts.
Not just harnesses, you can even use the subscription in CI/CD. That, plus the fact that web chat does not count toward the same limits, is why I think the Codex personal plan is easily 10x the value of Claude Code. https://developers.openai.com/codex/auth/ci-cd-auth
Re: GPT-5.5 Codex reasoning-token clustering may be leading to degraded performance
#155Indeed, it looks like my work has suffered from the clustering issue as well: reasoning_output_tokens count percent ━━━━━━━━━━━━━━━━━━━━━━━━━ ━━━━━━━ ━━━━━━━━━ 0 873 28.5948 ───────────────────────── ─────── ───────── 8 64 2.0963 ───────────────────────── ─────── ───────── 9 60 1.9653 ───────────────────────── ─────── ───────── 11 54 1.7688 ───────────────────────── ─────── ───────── 516 48 1.5722 ───────────────────…
When I reviewed the conversations affected by this issue, they did not always align with my feeling of "degraded output". Some were definitely below par, and I recall having to iterate on the generated code more than I wanted to. However, it is only true for a very small number of conversations. So we're looking at a small set of affected conversations, and even within that small set, only a few will have degraded ou…
There seems to be something wrong with the "commentary" channel related intermediate updates, maybe the model gets confused about what's an intermediate update vs what's the final answer? [1]
[1] https://github.com/openai/codex/issues/30364#issuecomment-48...
Re: GPT-5.5 Codex reasoning-token clustering may be leading to degraded performance
#156Re: GPT-5.5 Codex reasoning-token clustering may be leading to degraded performance
#157Earlier quoted context omitted.
And although Codex Desktop is not open source (AFAIK), it does expose CDP and appserver which allowed me to build a Greasemonkey-like plugin system on top of it. It's surprisingly powerful, you can add transcript annotations, programmatically control the side panels, integrate a native-looking account switcher, and so on.
This sounds really cool. Do you have the source published anywhere?
Warning: I use this daily myself for work, but beyond me arguing with it to get the CDP architecture, this was completely vibe-coded. I mostly use vim mode (jump to line, jump to prev/next user message) and the account switcher.
Re: GPT-5.5 Codex reasoning-token clustering may be leading to degraded performance
#158Earlier quoted context omitted.
Verified this locally myself. Thanks for the concrete test. I guess it's time to give Claude another try.
This is preliminary, but it seems like it might somehow be related to the `## Intermediary updates` system prompt that's provided to the model. Seems like it forces the model to stop thinking and return early to provide updates. Removing that entirely makes all runs succeed [1]. I wonder if it's somehow getting confused between what's supposed to be an intermediate update vs the final result. [1] https://github.com/o…
Re: GPT-5.5 Codex reasoning-token clustering may be leading to degraded performance
#159Re: GPT-5.5 Codex reasoning-token clustering may be leading to degraded performance
#160Earlier quoted context omitted.
I have a philosophical problem with adaptive thinking. It’s a dumb guess for how much thinking budget to allocate ahead of thinking. At least in the context of LLMs there is probably no way of knowing how much thinking (token generation) is needed. The problem space is infinity vast, similarly of two prompts is not going to help any LLM decide how much thinning is needed. Models already stop thinking before hitting t…
At least there should be a tool call that's the equivalent of saying "wow, this is more complicated than I thought". Humans are also often prone to under-allocating reasoning time and coming to wrong conclusions because their reasoning ends up too shallow. But the best humans are great at mentally mapping the problem space and readjusting on the fly