OpenAI Announces GPT-5.1-Codex-Max With Day-Long Autonomous Coding Sessions
Description
A screenshot of a social media post from someone at OpenAI announcing GPT-5.1-Codex-Max, a model that 'can work autonomously for more than a day over millions of tokens.' The post states 'Pretraining hasn't hit a wall, and neither has test-time compute.' It congratulates teammates @kevinleestone and @mikegmalek. Below the text is a technical description of long-running tasks and a line chart comparing GPT-5.1-Codex and GPT-5.1-Codex-Max on a 'Verified (n=500)' benchmark. The X-axis shows 'Thinking tokens' from 0 to 35,000 and the Y-axis shows difficulty levels solved (low, medium, high, xhi). The Codex-Max model (darker line) significantly outperforms the regular Codex model at higher thinking token budgets, reaching 'xhi' difficulty at 35k tokens. The text describes how Codex-Max automatically compacts its session when approaching context window limits, pruning history while retaining the most important context
Comments
30Comment deleted
GPT-5.1-Codex-Max can work for 24 hours straight on your codebase -- finally an engineer that matches the expectations in the job posting
An AI that runs for 24 hours? Perfect. It can finally finish running 'npm install' on our legacy frontend project
And also max is actually xhigh but please, move along, less questions Comment deleted
still an improvement I guess? Comment deleted
Meh You know that I'm LLMs lover But this looks like shareholder-pleasing bullshit / damage control Gemini-3 is innovation Release of Sonnet-4.5 and Opus 4/4.1 were innovation This max which is actually xhigh looks like total bullshit Needs testing though Comment deleted
The only sad part about gemini-3 is that I only have access to pro, and not to gemini-3-ultra 🌚🌚🌚 But I can live with that Comment deleted
less tokes for same result seems like an ok improvement, though obv the headline is bs Comment deleted
Here the problem - this graph is for n=500 Comment deleted
meaning? Comment deleted
500 attempts Comment deleted
oh, shitty sample size. alright sure Comment deleted
Its like averages success rates If you want better codegex DX you want to see zero-shot improvements Comment deleted
yknow, if this was a good graph, they'd show inaccuracy ranges on the graph… Comment deleted
Well, OAI is famous for their charts after all 😄 Comment deleted
it's become a rather famous statement, but it's still true: never trust a statistic you haven't faked yourself Comment deleted
Kinda missed it, why is gemini 3 considered innovation? Pretty strong word for a current state of the llms Comment deleted
Because funny numbers on stock exchanges go up Comment deleted
innovation in finance unprecedented stock inflation Comment deleted
So sad about those remaining 5% engineers who debug mess left after 95% Comment deleted
I assume that includes "hey codex, refactor this- oh it ran rm -rf again" Comment deleted
Industry: PRs must be small and on point so its easy to properly review them OAI: IMAGINE HOW MUCH WORK IT CAN DO IN 24 HOURS OF CODEGEN?! Comment deleted
I come up with what useful it may work on for 24 hours It stopped after 10 minutes with 80% free context 😕 Comment deleted
Tried 5.2? Comment deleted
but what for though Comment deleted
Yeah, thats the entire point of my rant in comments for this screenshot 😄 Comment deleted
just wanted to put it into 4 words Comment deleted
+1 Comment deleted
Thats not so practically usable for codegen / doesnt look like something that will translate into meaningful improvement Comment deleted
OpenAI hasn't yet learned more compute can't fix fundamental limitations. That adding 10k more GPUs doesn't make ChatGPT make shit up less Comment deleted
Did they just add "try again" in system prompt and some sort of context summarisation ? Comment deleted