Codex Gets Chrome DevTools Protocol Access in New Developer Mode
Codex's new Developer mode gives the agent controlled CDP access to profile JavaScript, inspect network traffic, and debug live browser state.
Codex can now see under the hood of the browser while it works. Version 26.609 of the Codex app, which shipped on June 11, 2026, introduces Developer mode: a controlled Chrome DevTools Protocol (CDP) integration that lets the agent profile JavaScript performance, inspect network requests, read console output, and examine DOM state and applied styles in real time.
If you have ever opened DevTools with F12 to figure out why a page is misbehaving, you already understand what this unlocks. Previously, Codex could see the rendered page. Now it can see what is happening beneath it.
What CDP Access Actually Gives Codex
The Chrome DevTools Protocol is the internal interface that external clients use to command a Chromium-based browser. It can ask Chrome to return a DOM snapshot, capture a performance trace, list pending network requests, or surface console messages and runtime errors. Opening that interface to Codex means the agent is no longer guessing at problems from the outside.
Practically, this means Codex can identify a slow JavaScript function without you pointing at it, catch a failed API call from the network panel, read the exact error thrown in the console, and check whether a CSS rule is actually being applied. That is the same diagnostic loop a developer runs manually, but now the agent runs it autonomously before suggesting a fix.
Browser use is also faster as a result. CDP and DOM snapshot optimisations reduce the number of browser round trips, and OpenAI says this has made browser use up to 2x faster overall.
How It Works Across the Two Browser Surfaces
Codex has two distinct browser environments, and CDP works across both.
The in-app browser is a clean, isolated environment inside Codex threads. It works with local development servers, file-based previews, and public pages. It does not carry your cookies, extensions, or login sessions, so it is not the right tool for anything that requires authentication. For debugging your own app running on localhost, though, it is the primary surface.
The Chrome extension handles the opposite case. When you need Codex to work on a page where you are already logged in, such as an internal tool, a CRM, or a web app with an authenticated session, you invoke it with @Chrome. Full CDP access is available there too, operating on the browser where your session already exists.
Turned Off by Default, With an Admin Override
Developer mode is off by default. Users enable it in Codex app settings, and it requires explicit approval on a per-site basis before CDP access is granted. If you have not turned it on, nothing changes for you.
For admins and workspace owners, there is a policy-level control. In the Policies and Configurations pane of Codex cloud settings, setting browser_use_full_cdp_access to false disables the feature across the workspace entirely. Disabling Browser use overall also disables CDP.
This matters. Full CDP access gives an agent the same depth of access to a browser session that a developer has. That is genuinely useful in a controlled development context. It is also a meaningful trust boundary, and the ability to turn it off at the admin level is the right way to handle that.
The /init Command and Rate-Limit Reset Banking
Two other additions shipped in the same release.
The /init command is now available in the app composer. It creates project instruction scaffolding using the same initialisation workflow as the Codex CLI. If you have been using the CLI to set up new projects and wishing that workflow existed inside the app, it now does.
Rate-limit reset banking is available for Plus and Pro users. At launch, eligible users receive one free reset. From there, you can send referral invitations directly from within the Codex app. When an eligible recipient sends their first Codex message, both parties receive a banked rate-limit reset, usable for 30 days after it is granted.
Business users have a parallel system. Workspace members can invite coworkers from the profile menu under “Invite a coworker,” and receive a referral bonus when the coworker joins the workspace and sends their first message. Admins can control this feature from Workspace settings under Permissions and Roles.
What This Means for You
If you are a developer using Codex to build or debug web applications, Developer mode closes a meaningful gap. An agent that can read the console, inspect network traffic, and profile JavaScript while fixing a bug is doing substantively more useful work than one that can only see the rendered output. The per-site approval requirement and the default-off state mean you stay in control of when and where that access is granted.
If you are an admin managing Codex for a team, the workspace-level kill switch via browser_use_full_cdp_access = false gives you a clean policy lever. You will want to make a deliberate decision about this rather than leaving it to chance, particularly for teams working with authenticated sessions via the Chrome extension.
For Plus and Pro users who hit rate limits regularly, the referral banking system provides a practical pressure valve. It is a modest mechanic but a useful one if you are doing heavy Codex work.
The /init command is a quality-of-life improvement that brings the CLI and app workflows closer together. Small, but welcome if project initialisation has been a context switch you have been managing manually.
The full release notes are available in the OpenAI Help Center, and the Codex-specific changelog is at developers.openai.com/codex/changelog.