Introducing upgrades to Codex
OpenAI
OpenAI just shipped a big upgrade to Codex, its coding agent, making it faster and more reliable everywhere you code.
Based on reporting by OpenAI — read the original for the full story.
Summary, retelling and take written by AI under human oversight; images are AI-generated illustrations. How we work · Report an error
OpenAI is rolling out updates to Codex, and the pitch this time is less about flashy new tricks and more about making the thing actually dependable. Speed and reliability are the headline words, which tells you where the complaints were probably piling up. Anyone who's used an AI coding assistant knows the gap between a demo that nails a clean function and a tool that survives a messy real-world codebase full of legacy quirks and half-documented dependencies.
The bigger shift is where Codex now lives. It's not confined to one interface anymore — you can work with it in the terminal, inside your IDE, through the web, or apparently from your phone. That last one is a small but telling detail. Coding agents are increasingly being framed less like a plugin and more like a colleague you can check in with from wherever you happen to be, even if you're away from your main machine.
OpenAI is also pushing harder on two fronts that pull in slightly different directions: real-time collaboration and independent task completion. The first assumes a developer sitting there, iterating with the model in the loop. The second assumes you hand off a task and walk away, trusting Codex to grind through it without hand-holding. Supporting both well is a harder engineering problem than it sounds, since the model has to know when to ask and when to just act.
None of this is revolutionary in isolation — faster inference and better reliability are the kind of upgrades every AI lab ships eventually. But coding tools live or die on trust, and trust is built through boring consistency, not viral demos. If Codex is genuinely more dependable across terminal, IDE, web, and mobile, that's the kind of unglamorous improvement that actually changes whether developers reach for it by default instead of as a novelty.
My take — AI-written commentary, not fact-checked reporting
I'll believe 'more reliable' when I see fewer developers quietly falling back to writing the tricky bits themselves — that's always been the real benchmark, not benchmarks. The push toward autonomous, hand-it-off coding agents is the part to watch, though; that's where the actual labor substitution happens, not in the chatty pair-programming mode everyone likes to demo.
Read more about this at: OpenAI