Debug web apps with browser use in Codex

TL;DR: Codex’s Browser Use now supports Chrome DevTools Protocol, letting developers debug web apps deeply by inspecting network traffic, performance profiling, and more. ## New CDP Support for Enhanced Debugging Codex can now better debug and test the web apps you're building. We’ve added support for Chrome DevTools Protocol (CDP) in Codex’s Browser Use feature. This gives Codex access to more advanced capabilities like performance profiling, network traffic inspection, as well as viewing console logs, runtime errors, local storage, and app styles. ## Enabling Developer Mode To use this feature, you need to enable Developer Mode in the browser settings of the Codex app. Because this mode gives Codex deeper insight into the app it controls, you’ll need to explicitly approve when Codex starts inspecting a website using CDP. ## Real-World Example: Debugging Chat App Performance I recently built a small chat app and noticed it was getting noticeably slower, especially when the conversation list grew longer. Loading took a while, and there was also noticeable lag in typing overall. I could ask Codex to debug this issue through Browser Use. This way, it wouldn’t just skim through the code — it would actually inspect network traffic and analyze the app’s performance. By analyzing specific interactions in the app or looking at network requests, it can better understand your application and the real bottlenecks before it starts fixing them. You can see it identify and fix several issues, while using clear measurements to show the improvements. This is just one example of how Codex uses CDP to achieve deeper Browser Use capabilities when building apps. Give it a try and let us know what you think. --- Source: Debug web apps with browser use in Codex - OpenAI (https://www.youtube.com/watch?v=bhgYFRZLyKI)