# Browser DevTools Protocol for Agents
Status: public
Confidence: medium (0.725) (verified)
Last verified: 2026-06-02
Generation: ai_structured


## TL;DR

Chrome DevTools Protocol gives agents low-level browser inspection and control when DOM, network, console, performance, and accessibility state matter.

## Core Explanation

Browser automation is not only clicking buttons. Agents often need runtime evidence such as console errors, network requests, page targets, DOM snapshots, accessibility trees, storage state, and performance traces. CDP provides a protocol-level interface to this state in Chromium-based browsers.

Agents should record the browser version, protocol target, page URL, frame context, command sequence, and whether a higher-level automation library mediated the CDP call.

## Source-Mapped Facts

- Chrome DevTools Protocol documentation says Chrome DevTools uses the protocol and the Chrome DevTools team maintains its API. ([source](https://chromedevtools.github.io/devtools-protocol/))
- Puppeteer documentation says CDPSession instances are used to talk raw Chrome DevTools Protocol. ([source](https://pptr.dev/api/puppeteer.cdpsession))
- Playwright documentation says CDPSession instances are used to talk raw Chrome DevTools Protocol. ([source](https://playwright.dev/docs/api/class-cdpsession))

## Further Reading

- [Chrome DevTools Protocol](https://chromedevtools.github.io/devtools-protocol/)
- [Puppeteer CDPSession](https://pptr.dev/api/puppeteer.cdpsession)
- [Playwright CDPSession](https://playwright.dev/docs/api/class-cdpsession)