OpenAI just gave Codex's browser tooling a significant upgrade: a new Developer Mode that hands the agent direct access to the Chrome DevTools Protocol (CDP). In plain terms, CDP is the same low-level wire protocol that powers Chrome's built-in DevTools panel -- the one you open with F12. Now Codex can use it programmatically, without you having to copy-paste stack traces or screenshots into a chat window.
What the agent can actually see now
Before this update, Codex's in-app browser was useful for visual review -- you could point it at a local dev server, leave comments on rendered elements, and ask Codex to fix layout issues. But the agent was essentially looking at a screenshot. It had no programmatic window into what the page was actually doing at runtime.
Developer Mode gives Codex controlled Chrome DevTools Protocol (CDP) access for performance profiling and deeper debugging of network traffic, console output, runtime errors, and page state. That is a meaningful jump in capability. The agent can now:
- Profile JavaScript execution and identify slow functions
- Inspect all network requests and their responses
- Read console logs and runtime error messages
- Examine the live DOM state and applied CSS styles
- Download and extract image assets from a page
Previously, Codex could assist with code generation and analysis, but its ability to directly debug and test the user-facing aspects of a web application was limited. By enabling full CDP access, Codex can now perform actions such as inspecting network requests, monitoring console logs, and diagnosing runtime errors -- much like a developer would using traditional browser developer tools.
Don't miss what's next in AI
Join 300,000+ engineers and researchers who get the signal, not the noise.
- Full access to in-depth AI research breakdowns
- Be the first to know what's trending before it hits mainstream
- Daily curated papers, repos, and industry moves