On June 12, the official OpenAI Developers account announced that Codex has launched a "Developer Mode" in both the Chrome browser and Codex's in-app browser.
The key to this update is not a gimmick: Codex can now use the Chrome DevTools Protocol (CDP) to debug the browser directly — meaning Codex, for the first time, can "see the real state of a page" instead of only reading source code, looking at screenshots, and guessing with an LLM.
What Codex Can Now Do
According to OpenAI's official description, Codex can do four things inside Chrome and the built-in browser:
- Capture and analyze JavaScript performance profiles
- Pull console output
- Inspect network traffic
- Inspect the current page state (including DOM, Storage, and more)
- June 11, 00:00: OpenAI announced it will acquire Ona, specifically to add "secure, persistent cloud environments" supporting "long-running AI agents"
- June 11, 23:58 (Beijing time): Codex launched rate-limit reset banking, giving each Go/Plus/Pro/Business user one free "banked reset"
- June 12, 00:11: Browser Developer Mode
- June 10: Qwen (via Oracle Cloud) committed access to OpenAI models and Codex
- For frontend developers: the experience of "AI watching DevTools and debugging alongside you" is about to become routine. CDP is the standard interface for plugging AI into the browser workflow.
- For AI engineers: CDP-style "letting AI perceive real-world state" is a broader paradigm — the same logic could extend to mobile ADB, embedded devices, and industrial control protocols. This Codex update is a miniature template.
- For those following agent governance: a browser agent that can read console, capture network traffic, and inspect the DOM raises the question: where are the permission boundaries? OpenAI did not discuss security details in depth this time, but the browser-side permission model is a question that must be answered next.
- Official announcement: https://x.com/OpenAIDevs/status/2065226355495895521
- Rate-limit reset banking: https://x.com/OpenAI/status/2065225362544726371
- Acquiring Ona: https://openai.com/index/openai-to-acquire-ona
In short: previously, if you asked Codex to fix a "sluggish page," it could only modify code based on experience and wait for you to refresh and check. Now it can act like a real frontend engineer — opening DevTools to read flame charts, find slow requests, and see which JavaScript is throwing errors.
Why the CDP Protocol Matters
CDP is the set of debugging interfaces that Chrome/Edge exposes to external programs; Chrome's own DevTools is built on top of it. By connecting to CDP, Codex is placed on the same toolchain as human developers. This both expands what Codex can do by an entire dimension and promises deeper integration with IDEs and local tools.
Context: Codex Is Becoming OpenAI's All-in-One Development Platform
Viewed alongside OpenAI's recent moves, this update is part of a clear pattern:
Codex is no longer a single form factor — not just a code completion box or an agent running in a terminal. Browser, terminal, long-horizon agents, cloud environments: OpenAI is packing capabilities into it on a weekly cadence.