chrome-cdp

Interact with a local Chrome browser via the Chrome DevTools Protocol.

4|Updated Feb 6, 2026

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

Ready to run

npx skills add https://github.com/TTAWDTT/Aelin --skill chrome-cdp-ttawdtt

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: chrome-cdp
Source: https://github.com/TTAWDTT/Aelin/tree/main/backend/deepagents_skills/chrome-cdp
Command: npx skills add https://github.com/TTAWDTT/Aelin --skill chrome-cdp-ttawdtt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Interact with a local Chrome browser session through the Chrome DevTools Protocol to inspect, debug, and automate tasks, with explicit user approval required for access.

Core Features & Use Cases

List open pages and view their URLs to understand current browser state.
Capture screenshots, evaluate JavaScript, navigate, and perform scripted interactions across tabs via a lightweight CLI.
Use cases include debugging page behavior, automating repetitive tasks, and inspecting page structure during development.

Quick Start

Install Node.js 22+ and enable Chrome remote debugging, then run the chrome-cdp CLI to list pages and connect to a target.

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 browser tasks using the DevTools Protocol?▼

You can automate Chrome browser tasks by using a lightweight WebSocket-based protocol to connect to a local Chrome instance with remote debugging enabled, allowing you to evaluate scripts and simulate interactions. This requires explicit user approval for access.

Can I capture screenshots and inspect open tabs in Chrome via CDP?▼

Yes, you can capture screenshots and inspect open tabs by connecting to the Chrome DevTools Protocol. The Skill lists open pages, views their URLs, and performs scripted interactions across tabs to help debug page behavior.

What do I need to connect to Chrome DevTools Protocol for local debugging?▼

To connect to Chrome DevTools Protocol for local debugging, you need a running Chrome instance with remote debugging enabled and a compatible Node.js 22+ runtime. A per-tab daemon is used to maintain connection stability during automation tasks.

Does Chrome DevTools Protocol automation work without a remote debugging port?▼

No, Chrome DevTools Protocol automation requires a running Chrome instance with remote debugging explicitly enabled. The Skill relies on this WebSocket connection to navigate pages, evaluate JavaScript, and capture screenshots under user approval.

Why does my Chrome CDP automation lose connection when switching tabs?▼

Chrome CDP automation can lose connection during tab switches, which is why this Skill uses a per-tab daemon for stability. This lightweight WebSocket-based approach ensures your debugging and scripted interactions persist across the targeted tab.

Is there a way to evaluate JavaScript in a local Chrome session from the command line?▼

You can evaluate JavaScript in a local Chrome session by running a lightweight CLI that connects via the Chrome DevTools Protocol. This allows you to inspect page structure, navigate, and execute scripts across open tabs with explicit user approval.