browser-cdp

Name: browser-cdp
Availability: InStock
Author: corellis

Connect to an in-container Chrome instance via CDP to reuse login state.

27|1|Updated Mar 19, 2026

Search Tags:#automation #authentication #cdp #chrome #session #browser #noVNC

Ready to run

npx skills add https://github.com/CorellisOrg/Corellis --skill browser-cdp-corellisorg

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: browser-cdp
Source: https://github.com/CorellisOrg/Corellis/tree/main/templates/skills/browser-cdp
Command: npx skills add https://github.com/CorellisOrg/Corellis --skill browser-cdp-corellisorg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Chrome-based session management is brittle when sites require login cookies; browser-cdp provides a reliable in-container control to reuse login state via CDP, eliminating manual cookie copying and env var tricks.

Core Features & Use Cases

In-container Chrome session: operate authenticated web apps through CDP without exporting cookies.
Login verification and data retrieval: fetch data from sites requiring login and verify user authentication status.
Safe orchestration: fallback to noVNC login flow when session expires or is invalid.

Quick Start

Navigate to an authenticated site using the in-container Chrome via CDP and fetch the required data.

Frequently Asked Questions about browser-cdp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate Chrome browser sessions without manually copying login cookies?▼

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.

What is Chrome DevTools Protocol and how does it handle authenticated web scraping?▼

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.

How do I fetch data from a website that requires login using a headless browser?▼

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.

Do I need noVNC to authenticate a browser automation session?▼

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.

Can I connect to Chrome via CDP on any port for session-based automation?▼

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.

What should I do when an authenticated browser session expires during automation?▼

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.