skills.rest
hueidou
hueidouCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

browser_cdp

Scans local CDP ports and attaches to Chrome instances for shared browser control.

Updated Aug 27, 2026
Search Tags:#playwright#cdp#chrome#privacy#browser-automation#port-scanning#remote-debugging
One-click install
npx skills add https://github.com/hueidou/CoCo --skill browser-cdp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browser_cdp
Source: https://github.com/hueidou/CoCo/tree/main/src/coco/agents/skills/browser_cdp
Command: npx skills add https://github.com/hueidou/CoCo --skill browser-cdp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables safe discovery, connection, and management of Chrome instances using the Chrome DevTools Protocol (CDP), addressing scenarios where multiple tools or agents need to share or debug the same browser while making privacy trade-offs explicit.

Core Features & Use Cases

  • Port scanning: Fast concurrent scanning of local CDP ports (default range 9000–10000) to discover connectable Chrome endpoints.
  • Attach to running Chrome: Connect to an existing Chrome process without terminating or affecting the original browser process.
  • Start with exposed CDP: Launch Playwright-managed browsers with an exposed CDP port so other tools can attach.
  • Session and lifecycle rules: Enforces single-workspace single-browser constraint, distinguishes stop semantics between attached and launched browsers, and supports cache clearing via CDP.
  • Privacy and safety: Explicitly warns that CDP mode exposes cookies, history, and page content and requires user confirmation before enabling.

Quick Start

Scan local ports and connect to a running Chrome at localhost:9222 after confirming the user understands that connecting via CDP exposes browser cookies and history.

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 a running Chrome instance via the Chrome DevTools Protocol?▼

To connect via the Chrome DevTools Protocol, you scan local CDP ports to discover active endpoints, then attach to the running Chrome process without terminating it. You must confirm you understand that CDP exposes cookies and history before connecting.

Can I use Playwright to launch a browser with an exposed CDP port for debugging?▼

Yes, you can launch Playwright-managed browsers with an exposed CDP port, allowing other tools or agents to attach for debugging or multi-agent sharing while enforcing a single-browser-per-workspace constraint.

How does CDP port scanning work for finding local Chrome endpoints?▼

CDP port scanning performs fast concurrent scanning of local ports, defaulting to the 9000–10000 range, to discover connectable Chrome endpoints and establish health-checked CDP connections to them.

Does attaching to Chrome via CDP expose my browser cookies and browsing history?▼

Yes, connecting via CDP exposes browser cookies, history, and page content. The system surfaces explicit privacy warnings and requires your confirmation before enabling CDP mode to ensure you understand the security trade-offs.

What happens if I try to manage multiple Chrome instances in the same workspace?▼

The system enforces a single-browser-per-workspace constraint, preventing multiple Chrome instances from being managed simultaneously within the same workspace to avoid session conflicts and ensure stable browser control.

Related Skills

Explore More Software Engineering Skills→
sanand0sanand0
11

devtools

Control Chrome via DevTools Protocol for browser testing and debugging.

Community
Advanced
xxihxxih
1

browser

Automate Chrome navigation, JavaScript execution, screenshots, and DOM selection via the Chrome DevTools Protocol on port 9222.

Community
Intermediate
yuexpsyuexps
3

browser_cdp

Connect to Chrome browsers via CDP and scan debugging ports.

Community
Intermediate
stellarlinkcostellarlinkco
2.7k

browser

Automate Chrome browser interactions via the Chrome DevTools Protocol.

Official
Intermediate