OpenAI has begun pushing Codex past code generation and into the live browser, granting its coding agent controlled access to the Chrome DevTools Protocol. Surfaced as a developer mode for browser use across both the in-app browser and Chrome, it lets Codex profile JavaScript performance and read into console output, network traffic, page payloads, and rendered state, the same low-level vantage a developer gets from the dev tools panel. It can also reach into and rewrite a site's DOM, opening the door to reshaping a page on the fly: recoloring a theme, adjusting spacing and fonts via annotations, or pulling structured data and assets from a page.

For now, this sits firmly in early territory. The mode is opt-in under Settings, gated behind a toggle that organizations can disable, and held back from the EEA, the UK, and Switzerland at launch. In practice, it runs slowly, overloads under pressure, and sometimes needs a restart, and the models still feel undertrained on the tooling; results arrive, but often only after careful prompting and several attempts.

What sets this apart from earlier setups is that similar inspection and control were already possible by wiring Codex or Claude to external connectors. Bringing it in-house, paired with Codex's own embedded browser, lets OpenAI build on top with its own data and tooling rather than leaning on third-party plumbing. It fits a wider push: days earlier, OpenAI moved to acquire Ona, formerly known as Gitpod, to give Codex persistent cloud environments for tasks that run for hours or days. With Codex now past five million weekly users, the browser operates in a future many anticipate, where an AI layer sits in front of the web and tailors what each person sees — a vision still gated by far faster models and infrastructure that do not yet exist at scale.