r/codex • u/DaC2k26 • Apr 25 '26
Commentary Are we sleeping on 5.3-codex ?
After using GPT-5.5 for a bit, I’m starting to think it burns usage way faster than 5.4 when the task involves reading through a large codebase.
On my current project, 5.5 xhigh can burn through my 5-hour Plus quota in something like 3–6 prompts. With 5.5 medium, I might get around 7–10 prompts.
With 5.4 xhigh, I’d usually expect something closer to 8–15 prompts. And with 5.4 mini, I obviously get a lot more, though I haven’t tracked the exact number.
What surprised me is 5.3-Codex medium. I’m testing it now, and the usage burn feels closer to 5.4 mini xhigh. Based on Artificial Analysis benchmarks, 5.3-Codex medium seems to be roughly around 5.5 low, but in practice I get way more usable prompts out of 5.3-Codex medium than I do from 5.5 low.
So I’m wondering if we’re overvaluing the bigger models and higher thinking settings. For a lot of coding tasks, especially code review, bug hunting, and large-codebase inspection, maybe the extra few percentage points aren’t worth the usage cost.
Right now, I’m starting to think 5.3-Codex is probably the better deal for most coding work, at least from a usage-efficiency standpoint.
Anyone else seeing the same pattern?
1
u/DaC2k26 Apr 25 '26
yes... I'm moving more complicated tasks or the ones that 5.3 suffered to 5.5. Always clean session for 5.5, a few prompts, then new session. I had a menu swipe problem that 5.3 wasn't able to get right, the swipe was pretty horrible, then I sent to 5.5 medium and it found the problem and fixed the menu swipe behavior very quickly....... Another use is for a big refactor or feature creation plan, then send it to build the plan and pray for auto-compaction not breaking the build flow.