cdp-browser-control

Connect to Chrome via CDP to automate browsers while preserving login state.

Updated May 12, 2026
One-click install
npx skills add https://github.com/YeomanYe/skills --skill cdp-browser-control
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cdp-browser-control
Source: https://github.com/YeomanYe/skills/tree/main/cdp-browser-control
Command: npx skills add https://github.com/YeomanYe/skills --skill cdp-browser-control

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses browser automation failures caused by security policies, read-only browser tiers, and isolated sessions by enabling direct Chrome CDP control with preserved login state.

Core Features & Use Cases

  • Preserve login state: reuse existing cookies and session data to maintain authenticated context during automation.
  • Direct CDP access: connect to Chrome via remote debugging port to bypass session isolation in standard automation tools.
  • Recovery & troubleshooting: provide steps to recover from ECONNREFUSED, WebSocket 404, and related CDP errors with minimal disruption.
  • Use Case: automate tasks on secured sites where normal automation is blocked, while keeping user login intact.

Quick Start

Launch Chrome with remote debugging port enabled, connect to it via CDP directly, and begin automated control while preserving the existing user session.

Frequently Asked Questions about cdp-browser-control

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

FAQPage Schema
How do I preserve login state and cookies during Chrome browser automation?

To preserve login state during browser automation, connect directly to Chrome via the remote debugging port using CDP, which allows reusing existing cookies and session data to maintain your authenticated context.

Why does Playwright fail with ECONNREFUSED or WebSocket 404 on port 9222?

ECONNREFUSED or WebSocket 404 errors on port 9222 occur when standard automation tools face session isolation or read-only environments, requiring a direct CDP connection to Chrome to bypass these security policies.

How do I bypass browser security blocks for automation on secured sites?

Bypassing browser security blocks involves enabling Chrome remote debugging and establishing a direct CDP connection, which circumvents standard tool restrictions and maintains your user session on secured sites.

Do I need to launch Chrome with remote debugging enabled to use CDP control?

Yes, you need to launch Chrome with the remote debugging port enabled to establish a direct CDP connection, which is required for bypassing session isolation and preserving authenticated states.

What is the best way to handle CDP session isolation in browser automation?

The best way to handle CDP session isolation is to connect directly to Chrome via its remote debugging port instead of using standard automation tools, effectively bypassing the isolated sessions that block automation.