chrome-cdp

name

chrome-cdp

description

Connect to user's local Chrome session. Inspect and interact with web pages in a headful browser shared with user cookies and login states — navigate pages, click buttons, take screenshots, test web apps in headful Chrome the user could see in real-time. Use for headful browser automation. This skill should be used when user says "use my browser", "open this page", "in my Chrome", "fill the form", "test in real browser", "show in browser", "my login account". Request explicit user approval before use.

Chrome CDP

Lightweight Chrome DevTools Protocol CLI. Connects directly via WebSocket — no Puppeteer, works with 100+ tabs, instant connection.

Constraints

MUST explicitly ask for user permission before use. Chrome CDP runs in a headful browser in user screen. Start using Chrome CDP without user confirmation is offensive. User refuse: PAUSE IMMEDIATELY.

The headful browser will be the Chrome that user uses everyday with cookies and login states. Social media interactions requires user confirm.

Use agent-browser skill instead if you need stateless and headless access to web pages.

Prerequisites

• Chrome (or Chromium, Brave, Edge, Vivaldi) with remote debugging enabled: open chrome://inspect/#remote-debugging and toggle the switch
• Node.js 22+ (uses built-in WebSocket)
• If your browser's DevToolsActivePort is in a non-standard location, set CDP_PORT_FILE to its full path

Commands

All commands use scripts/cdp.mjs. The <target> is a unique targetId prefix from list; copy the full prefix shown in the list output (for example 6BE827FA). The CLI rejects ambiguous prefixes.

List open pages

scripts/cdp.mjs list