It lets the model inspect runtime errors and DOM state
Introducing developer mode for browser use in Chrome and the Codex in-app browser.
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.
Positive users hail Codex's new Chrome Developer Mode and CDP support as a huge debugging improvement, while negative users complain about unrelated bugs in Computer Use and demand the return of 4o.
Great ship by the browser team! Make sure to give @JamesZmSun a follow!
Introducing developer mode for browser use in Chrome and the Codex in-app browser.
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.
https://developers.openai.com/codex/app/browser#developer-mode
@JamesZmSun Can someone please take a look at the bug on Locked Computer Use please?? It’s been out for a few weeks not, but the bug persists
@Ray_DaHero @OpenAIDevs @reach_vb We’re aware of this issue and working to resolve it!
Be careful when using CDP with Chrome.
CDP is powerful. If you expose your everyday Chrome session, an agent may be able to inspect or control tabs, cookies, localStorage, network traffic, console output, and page state.
Use a dedicated throwaway profile, not your personal one.
Codex's in-app browser is the safer default if you don't need real-profile access.
@DicksonPau @JamesZmSun Sorry! What’s the bug?
@OpenAIDevs I have completely lost access to In-App Browser and Computer use after this update instead... Can this be looked into?
#Codex #OpenAI @reach_vb
1. Locked Computer Use runtime failure: Computer Use works while the Mac is unlocked. After locking the Mac, list_apps still works, which means the helper is reachable, but get_app_state("Finder") hangs and times out after 120 seconds. So the locked-screen app/window reading path is failing.
2. Install / authorization verification issue: The lock-screen component appears to be in an inconsistent state. The installer/status check has at times reported not-installed even though the SecurityAgent plugin bundle exists, and the installed authorization plugin fails codesign verification with “invalid signature.” So the system may not be reliably proving that the lock-screen authorization component is correctly installed, trusted, or activated.
@OpenAIDevs Cool, making web app then (+iOS) 😂 thx @dkundel
@AriX @JamesZmSun Let me DM you thank you!
@OpenAIDevs Good. Now Codex can see the same broken page the rest of us stare at for 20 minutes.
@OpenAIDevs Oh okay more stuff nobody asked for. How about you listen to your customers and give us back 4o. #keep4o
@JamesZmSun Awesome! Is it smart enough to use the right chrome profile when running multiple chats that should use different profiles?
@JamesZmSun great work!
@OpenAIDevs When available in Spain for pro max ultra users ?
@OpenAIDevs tysm
@OpenAIDevs But you know that a JavaScript console log can easily eat up to 5Mio token in 30 error calls?
@OpenAIDevs Yay
@OpenAIDevs amazing new feature! can we also see the image of the corgi that was generated perchance?😅
@OpenAIDevs Hey! I built that from scratch last month!!! Thank you very much!!
It lets the model inspect runtime errors and DOM state
Introducing developer mode for browser use in Chrome and the Codex in-app browser.
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.