Craft Chrome Devtools Protocol (CDP) commands with new command editor (developer.chrome.com)

So many people building AI browsers definitely had this as an internal tool already lol, nice to see Chrome leaning in here; CDP is a huge pain to write and debug

very nice. there are things that won't show up in the network panel and you had to resort to proxy for debugging, especially when you are using puppeteer/etc for testing.

FYI it's behind a feature flag (aka experiment). Just in case you rarely use experiments in DevTools:

DevTools -> Settings (cog, top right) -> Experiments -> Search for "Protocol Monitor" -> Check the checkbox

Awesome, debugging is gonna be way easier from here on out.

[dead]

Very useful. Does anything similar exists for Firefox?

[dead]

CDP is a good exmaple of why the ecosystem has converged around Chrome and not Firefox. CDP has:

- Full documentation

- A stable API

- Tooling like this

Firefox has none of that: implementing the firefox devtools protocol means reverse engineering it, and then sometimes it still breaks when Firefox updates!

Is this supported through the chrome dev tools mcp server?

Can anyone tell me some use cases for CDP commands?

In which situation is preferable to use CDP commands over Puppeteer?

I believe CDP is how Decky Loader (the homebrew sidebar for SteamOS works). It attaches to the web app that draws SteamOS's UI and injects its own plugins to the sidebar.