chrome-cdp

Automating Chrome via the DevTools Protocol (CDP) securely requires explicit user approval for headful interactions to ensure safe and auditable operations. This approach uses a per-tab daemon and a deterministic command surface to prevent unintended actions during automated testing and debugging workflows.

To start controlling a local Chrome session with CDP commands, you need to open Chrome with remote debugging enabled. Once active, you can issue deterministic commands like list, nav, eval, and click to automate inspection and testing workflows across open tabs.

Yes, CDP automation supports simulating user interactions like clicking and typing through dedicated commands. You can use click, clickxy, and type commands to script deterministic user flows, capture screenshots, and inspect the DOM during automated testing.

Yes, you can capture network activity and take screenshots while debugging a Chrome tab using specific CDP commands. The net command logs network requests, while the shot command captures visual snapshots, enabling comprehensive inspection of user flows and page states.

CDP browser automation requires explicit consent for headful interactions to maintain secure, auditable operations and prevent unauthorized scripts from controlling your browser. This safety prompt ensures that automated debugging and inspection workflows only execute with the user's direct permission.