browser-cdp

Control login state via Chrome DevTools Protocol (CDP) to reuse authenticated browser sessions without manually copying cookies. By connecting to a running Chrome instance through CDP, you can maintain login state directly and avoid brittle cookie management for web automation tasks.

Chrome DevTools Protocol (CDP) is a debugging interface that allows programmatic control of a running Chrome instance. It handles authenticated web scraping by reusing an active login session within the browser, enabling data retrieval from sites that require authentication without exporting or injecting login cookies.

Fetch data from login-required websites by navigating to the site using an in-container Chrome instance controlled via CDP. After establishing the initial login state, you can retrieve data directly through the authenticated session without needing to handle login forms or manage authentication tokens programmatically.

You need noVNC for the initial authentication flow when establishing a new login state in the container. Once authenticated, subsequent browser automation tasks connect directly via CDP, but noVNC serves as a fallback to re-authenticate if the login session expires or becomes invalid.

Chrome must be accessible on 127.0.0.1:9222 for CDP session-based automation. The Skill targets this specific local endpoint to connect to the running Chrome instance, verify login status, and execute authenticated data retrieval or web interaction tasks.

When an authenticated browser session expires during automation, you should re-authenticate using the noVNC login flow. The Skill provides safe orchestration by falling back to this noVNC interface to restore login state before resuming CDP-controlled data retrieval or website interaction.