browser_cdp

Manage Chrome sessions through the Chrome DevTools Protocol endpoint.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables explicit control of a Chrome browser through the Chrome DevTools Protocol (CDP), allowing you to connect to a running browser, scan for CDP ports, or share a single browser instance across multiple agents while guarding sensitive data.

Core Features & Use Cases

  • Scan local CDP ports to discover attach targets and connect to an existing Chrome session.
  • Attach to an already-open Chrome instance via a local CDP URL to reuse login state and tabs.
  • Start or configure a browser with an explicit cdp_port to enable cross-workspace sharing, with safeguards to avoid port conflicts.
  • Manage browser lifecycle with clear stop semantics (disconnect vs. closing the external browser) and privacy controls (private_mode).

Quick Start

Attach to a running Chrome by providing its local CDP URL, or start a new browser with a fixed CDP port.

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 browser via CDP?

To connect to a running Chrome browser via CDP, you can provide the local CDP URL to attach to the existing instance. This allows you to reuse the current login state and tabs without launching a new browser.

How do I share a single Chrome browser instance across multiple agents?

You can share a single Chrome browser instance across multiple agents by starting the browser with an explicit cdp_port. This enables cross-workspace sharing while enforcing a single browser instance per workspace to avoid port conflicts.

Can I scan local CDP ports to discover available Chrome attach targets?

Yes, you can scan local CDP ports to discover available attach targets. This feature helps you identify active Chrome sessions and connect to an existing browser session for direct management.

Does managing a browser via CDP support privacy controls and clear stop semantics?

Yes, managing a browser via CDP includes privacy controls like private_mode and explicit stop semantics. You can safely disconnect from the session without forcibly closing the external browser.

What is the limit on browser instances per workspace when using CDP?

The system enforces a single browser instance per workspace when using CDP. This limitation ensures stable cross-workspace sharing and prevents port conflicts when attaching to or launching Chrome sessions.