browser_cdp

Scan local Chrome CDP endpoints, attach to sessions, or start a browser with an exposed port.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/Jacksonhuf/AxiMate --skill browser-cdp-jacksonhuf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser_cdp
Source: https://github.com/Jacksonhuf/AxiMate/tree/main/integrations/ripple/copaw/src/copaw/agents/skills/browser_cdp
Command: npx skills add https://github.com/Jacksonhuf/AxiMate --skill browser-cdp-jacksonhuf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables safe and controlled CDP-based browser control by allowing you to discover local Chrome instances, attach to an existing Chrome session, or start a browser with an exposed CDP port. It also enforces privacy awareness and a single-workspace constraint.

Core Features & Use Cases

  • Scan local CDP ports to identify running Chrome instances.
  • Attach to an existing Chrome via connect_cdp without interrupting the process.
  • Start a Chrome with a CDP port exposed for external tools while clearly communicating privacy risks and the single-instance rule.

Quick Start

Choose an action: scan for CDP targets, connect to CDP at a URL, or start a browser with a CDP port, and proceed.

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 session using CDP without interrupting it?

To connect to Chrome via CDP without interrupting it, you attach to the running session using the connect_cdp mode, which links your automation tools to the active browser process seamlessly. This avoids restarting the browser.

How can I scan local ports to discover running Chrome CDP targets?

You can discover running Chrome CDP targets by using the list_cdp_targets mode, which scans local CDP ports to identify available Chrome instances for automation and debugging.

What is the best way to expose a Chrome browser CDP port for external tools?

The best way to expose a Chrome CDP port is by using the start mode with a specified cdp_port, which launches a browser instance accessible to external tools while enforcing a single-workspace rule to prevent conflicts.

Does CDP remote-debugging work with Playwright for browser automation?

Yes, CDP remote-debugging integrates with browser automation frameworks like Playwright by attaching to an exposed CDP port or connecting to an existing Chrome session, enabling external control over the browser instance.

What are the privacy risks of exposing a Chrome CDP port for debugging?

Exposing a Chrome CDP port carries privacy risks because it allows external tools to access and control the browser session, potentially exposing sensitive data; the skill provides safety notes to mitigate these risks.

Why does my CDP connection fail when multiple browser instances are running?

CDP connection may fail due to a single-workspace constraint, which restricts operations to one browser instance at a time to ensure safe and controlled browser control without session conflicts.