chrome-cdp

Automate Chrome tab tasks via raw WebSocket CDP commands in Node.js 22+.

102|4|Updated Apr 15, 2009

Search Tags:#automation #devtools #cdp #chrome #websocket #browser-debugging

Ready to run

npx skills add https://github.com/mikker/dotfiles --skill chrome-cdp-mikker

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: chrome-cdp
Source: https://github.com/mikker/dotfiles/tree/main/agents.symlink/skills/chrome-cdp
Command: npx skills add https://github.com/mikker/dotfiles --skill chrome-cdp-mikker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automates direct interaction with a local Chrome session via the Chrome DevTools Protocol (CDP) to enable focused tasks without heavier tooling.

Core Features & Use Cases

List open pages and identify distinct targets for automation.
Take viewport screenshots, read page content, and inspect the network timeline.
Evaluate JavaScript, navigate to URLs, and interact with page elements programmatically.
Real-world use: QA engineers can quickly script a page check, capture state, and verify behavior across tabs.

Quick Start

Open Chrome with remote debugging enabled, then use the cdp CLI to list open targets and interact with a selected page.

Frequently Asked Questions about chrome-cdp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate Chrome DevTools Protocol tasks without Puppeteer?▼

You can automate Chrome DevTools Protocol tasks without Puppeteer by using raw WebSocket CDP commands and per-tab daemons to interact directly with a local Chrome session for navigation, screenshots, and JavaScript evaluation.

What can I do with direct Chrome DevTools Protocol automation?▼

Direct Chrome DevTools Protocol automation allows you to list open targets, navigate URLs, capture viewport screenshots, evaluate JavaScript, inspect network events, and interact with page elements programmatically across multiple tabs.

Do I need to launch Chrome with remote debugging enabled to use CDP automation?▼

Yes, you must open Chrome with remote debugging enabled to establish a connection before using a CDP CLI workflow to list open targets and interact with selected pages.

What is the best way to inspect network events across multiple browser tabs?▼

The best way to inspect network events across multiple browser tabs is using a deterministic CLI workflow that employs per-tab daemons and raw WebSocket CDP commands to monitor the network timeline for each target individually.

Can I evaluate JavaScript on a specific page tab using Chrome DevTools Protocol?▼

Yes, you can evaluate JavaScript on a specific page tab by identifying distinct targets through the CDP CLI and sending raw WebSocket commands to execute scripts programmatically within that local Chrome session.

What are the limitations of using raw WebSocket CDP commands for browser debugging?▼

Raw WebSocket CDP commands require a Node.js 22+ environment, explicit user approvals for deterministic execution, and managing per-tab daemons manually without the higher-level abstractions provided by heavier tooling like Puppeteer.