I keep a small folder of OpenAI Codex release notes in my bookmarks bar, and this week I caught a quiet one I almost missed. PR 33972, merged July 18 into the release/0.144 branch by sayan-oai, lowered the bundled model metadata's context-window number from 372,000 tokens to 272,000 tokens. That is roughly a 27 percent reduction in advertised capacity for gpt-5.6-sol inside Codex. The PR title is "Backport refreshed bundled model metadata to 0.144", which sounds boring, and the diff is 64 additions and 54 deletions against a single JSON metadata file. To be fair I would take the literal 27 percent with a grain of salt because the JSON is the bundled-config number, not a server-side enforcement knob — but the practical reading is that any harness still asserting 372k as the window is now wrong, and OpenAI's own Codex release notes for 0.144.6 confirm the cap is back at 272k.
The angle that grabbed me, and what I want to put down here, is that the reduction is happening at the same time that harnesses outside Codex are configured against the older 372k number, and Kun Chen's X post from July 13 flagged this directly: "important tip if you are using gpt 5.6 but not through codex, OpenAI just pointed out requests beyond 272k tokens are over-charged, and many harnesses right now set gpt 5.6 context window at 372k, which will cause you to lose quota more quickly than it should". His specific remediation was telling Pi to change its gpt-5.6 context window to 272k. The Reddit thread on r/codex picked it up the same day with 90 upvotes and 83 comments, mostly engineers saying they had no idea the harness default was still 372k. OpenAI's response on the same channel framed it as "No nerfing, only good stuff!" plus a 10 percent usage bump from inference optimizations landing on the Sol subscriptions. My gut says both can be true at once — the inference savings are real, and the older harnesses are still over-charging on requests they think fit in 372k but actually do not.
The reason I want to write this down is that I run gpt-5.6-sol through both Codex and a couple of non-Codex harnesses for the projects I am shipping this quarter, and I had assumed my context-window setting was correct because the picking roundups I read in late June still quoted 372k as the headline number for Sol. The picking-roundup framework that ranks IDE workflow and code generation on S/A/B/D tier letters and 9.6-out-of-10 decimal scores does not have a column for the actual configured window versus the marketed window — and the pricing-guide framework that prices Gemini Pro at 19.99 dollars per month, ChatGPT Plus at 20 dollars, and Claude Pro at 20 dollars does not have a row for the gpt-5.6 over-charge delta. The format-vs-format drift I wrote about earlier this month is now showing up inside the same week as a token-billing change that the format cannot measure, because the format is sorting on tier letters and dollars and not on what the harness thinks the window is.
The practical takeaway I want to write down is that I went through my own harnesses this morning and found one Pi configuration still set to 372k and one Cursor-side agent loop still asserting the older window in its prompts, both of which I changed to 272k. Honestly I am a little skeptical that this is the kind of change most engineers will catch from the picking scorecards, because the scorecards measure chat quality and pricing tier and not configured window, and the over-charge shows up as a slightly faster quota burn rather than a visible error. The companion PR 34009 and the release tag rust-v0.144.6 are the references worth bookmarking if you are running gpt-5.6-sol through anything other than Codex itself.
I will reassess in three months. For now I have set every gpt-5.6-sol harness I touch to 272k, and I have started keeping a per-harness log of which window number each one is configured against because the picking roundups are not going to surface this. Give it six months and I expect either the picking roundups to add a configured-window column or the harness vendors to start pinning 272k as a default the way Codex just did, and whichever moves first will tell me whether the format has finally noticed that the marketed window and the configured window can drift inside a single quarter without anyone catching it on the scorecard.
Top comments (0)