browser_cdp

Connect to and manage Chrome/Chromium browsers via CDP with port scanning.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/9999-12-31/Dr.Claw --skill browser-cdp-9999-12-31
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser_cdp
Source: https://github.com/9999-12-31/Dr.Claw/tree/main/src/qwenpaw/agents/skills/browser_cdp-en
Command: npx skills add https://github.com/9999-12-31/Dr.Claw --skill browser-cdp-9999-12-31

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Connect to and manage a Chrome/Chromium browser via CDP, enabling explicit connections, port scanning, and cross-agent sharing while keeping data exposure under control.

Core Features & Use Cases

  • Scan local CDP ports and connect to an existing Chrome instance
  • Attach to a running browser and share a single browser across multiple agents/tools
  • Use an explicit cdp_port when needed, or connect via a provided cdp_url for external tools

Quick Start

Connect to a running Chrome or scan for available CDP targets to begin controlling a browser.

Frequently Asked Questions about browser_cdp

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

FAQPage Schema
How do I connect Playwright to an existing Chrome browser using CDP?

You can connect to an existing Chrome browser via CDP by scanning local ports for available targets or by attaching directly to the running instance using explicit connect_cdp actions.

Can I share a single Chrome browser across multiple automation agents?

Yes, you can share a single browser across multiple agents by attaching to a running instance and exposing it over CDP using a fixed port or a remote cdp_url for external tools.

How do I scan for available Chrome DevTools Protocol endpoints locally?

You can scan for available CDP endpoints by checking local ports to discover running Chrome instances, allowing you to attach to and manage the browser explicitly.

What are the privacy implications of connecting to a browser via a remote CDP URL?

Connecting to a browser via a remote CDP URL introduces data exposure risks; the system explicitly warns about these privacy implications when establishing remote connections for external tools.

Why am I limited to one browser per workspace when using CDP connections?

The one-browser-per-workspace rule is imposed when using CDP connections to manage explicit connections and cross-agent sharing effectively, preventing conflicts when attaching to running instances.