browser_cdp

Connect to or manage Chrome browsers via CDP by scanning ports or specifying a cdp_port.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Connect to or manage a Chrome browser via CDP by scanning ports, attaching to an existing instance, or sharing a single browser across agents.

Core Features & Use Cases

  • Scan local CDP ports to discover attach targets on the machine.
  • Connect to an existing Chrome instance via a CDP URL (for example, http://localhost:9222) to take control without launching a new browser.
  • Launch a browser with an explicit cdp_port to facilitate external sharing and multi-agent coordination.
  • Privacy guidance: use private_mode=true to avoid exposing history, cookies, or sensitive data, and understand the single-browser-per-workspace constraint.

Quick Start

Start a managed or shared Chrome session by specifying a cdp_port in the start action, for example start with {"action": "start", "cdp_port": 9222}.

Frequently Asked Questions about browser_cdp

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

FAQPage Schema
How do I connect to an existing Chrome instance via CDP without launching a new browser?

You can connect to an existing Chrome instance via CDP by providing a specific CDP URL, such as http://localhost:9222, to attach directly. This enables taking control of the browser without launching a new instance.

How do I discover available Chrome remote debugging targets on my machine?

You can discover available Chrome remote debugging targets by scanning local CDP ports. This port-scanning feature identifies active attach targets on your machine, enabling explicit CDP control.

Can I share a single Chrome browser across multiple agents using CDP?

Yes, you can share a single Chrome browser across multiple agents by launching it with an explicit cdp_port. This setup facilitates external sharing and multi-agent coordination, though it is constrained to one browser per workspace.

What is the single-browser-per-workspace constraint in remote debugging?

The single-browser-per-workspace constraint limits remote debugging sessions to one managed Chrome browser instance per workspace. This limitation ensures stable CDP port-scoped connections and prevents conflicts during multi-agent browser sharing.

How do I use private_mode to protect sensitive data during browser automation?

To protect sensitive data during browser automation, use private_mode=true when starting your CDP connection. This prevents the browser from exposing your history, cookies, and other sensitive information.