Codex adds Chrome Developer Mode support with full CDP access

OpenAI has just rolled out a new “Developer mode” for Codex browser use, enabling Chrome DevTools Protocol access to profile JS performance and inspect console, network, and page state. Settings flag “Elevated risk,” warning full CDP access can expose sensitive browser internals.

Codex adds Chrome Developer Mode support with full CDP access

TL;DR

  • Developer mode for browser use: Added for Chrome and the Codex in-app browser
  • CDP-based debugging: Codex can profile JS performance; inspect console output, network traffic, and page state
  • Settings flag elevated risk: “Developer mode” section labeled “Elevated risk” with “Enable full CDP access”
  • Security warning: Full CDP access can inspect/control sensitive browser internals, increasing data exposure risk

OpenAI Developers introduced a “developer mode” for browser use in Chrome and the Codex in-app browser, saying Codex can use the Chrome DevTools Protocol (CDP) to debug browser issues by profiling JavaScript performance and inspecting console output, network traffic, and page state.

The accompanying settings views appear to place the feature under a “Developer mode” section marked “Elevated risk,” with an option to “Enable full CDP access.” The description warns that full CDP access lets Codex “inspect and control sensitive browser internals” that may put data at risk.

Reactions on X ranged from enthusiasm to caution. Some users described CDP access as useful for debugging, while one commenter warned that exposing a normal Chrome session could let an agent inspect or control tabs, cookies, localStorage, network traffic, console output, and page state, recommending a throwaway profile instead.

Source: OpenAIDevs on X

Continue the conversation on Slack

Did this article spark your interest? Join our community of experts and enthusiasts to dive deeper, ask questions, and share your ideas.

Join our community