chrome-cdp

name	chrome-cdp
description	Interact with local Chrome browser session (only on explicit user approval after being asked to inspect, debug, or interact with a page open in Chrome)

Chrome CDP

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

Prerequisites

• Chrome (or Chromium, Brave, Edge, Vivaldi, Helium) 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

Multiple browsers

The user runs two browsers with CDP enabled. To target a specific one, set CDP_PORT_FILE:

Browser	CDP_PORT_FILE
Helium	~/Library/Application Support/net.imput.helium/DevToolsActivePort
Chrome	~/Library/Application Support/Google/Chrome/DevToolsActivePort

Example:

CDP_PORT_FILE=~/Library/Application\ Support/net.imput.helium/DevToolsActivePort scripts/cdp.mjs list
CDP_PORT_FILE=~/Library/Application\ Support/Google/Chrome/DevToolsActivePort scripts/cdp.mjs list

Without CDP_PORT_FILE, the tool picks whichever DevToolsActivePort it finds first. Always list both when the user asks about browsers.

Commands

The CDP CLI lives at /Users/duarteocarmo/.agents/skills/chrome-cdp/scripts/cdp.mjs. Use this absolute path unless your current working directory is the skill directory. Do not assume scripts/cdp.mjs exists in the project/current directory.

All commands use the CDP CLI. 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

Take a screenshot

scripts/cdp.mjs shot <target> [file]    # default: screenshot-<target>.png in runtime dir

Captures the viewport only. Scroll first with eval if you need content below the fold. Output includes the page's DPR and coordinate conversion hint (see Coordinates below).

Accessibility tree snapshot

scripts/cdp.mjs snap <target>

Evaluate JavaScript

scripts/cdp.mjs eval <target> <expr>

Watch out: avoid index-based selection (querySelectorAll(...)[i]) across multiple eval calls when the DOM can change between them (e.g. after clicking Ignore, card indices shift). Collect all data in one eval or use stable selectors.

Other commands

scripts/cdp.mjs html    <target> [selector]   # full page or element HTML
scripts/cdp.mjs nav     <target> <url>         # navigate and wait for load
scripts/cdp.mjs net     <target>               # resource timing entries
scripts/cdp.mjs click   <target> <selector>    # click element by CSS selector
scripts/cdp.mjs clickxy <target> <x> <y>       # click at CSS pixel coords
scripts/cdp.mjs type    <target> <text>         # Input.insertText at current focus; works in cross-origin iframes unlike eval
scripts/cdp.mjs loadall <target> <selector> [ms]  # click "load more" until gone (default 1500ms between clicks)
scripts/cdp.mjs evalraw <target> <method> [json]  # raw CDP command passthrough
scripts/cdp.mjs open    [url]                  # open new tab (each triggers Allow prompt)
scripts/cdp.mjs stop    [target]               # stop daemon(s)

Coordinates

shot saves an image at native resolution: image pixels = CSS pixels × DPR. CDP Input events (clickxy etc.) take CSS pixels.

CSS px = screenshot image px / DPR

shot prints the DPR for the current page. Typical Retina (DPR=2): divide screenshot coords by 2.

Tips

• Prefer snap --compact over html for page structure.
• Use type (not eval) to enter text in cross-origin iframes — click/clickxy to focus first, then type.
• Chrome shows an "Allow debugging" modal once per tab on first access. A background daemon keeps the session alive so subsequent commands need no further approval. Daemons auto-exit after 20 minutes of inactivity.