skills/pasky__chrome-cdp-skill
1
0
Fork 0
mirror of https://github.com/pasky/chrome-cdp-skill.git synced 2026-09-19 04:47:42 +08:00
Code Issues Packages Projects Releases Wiki Activity

Restore Why not chrome-devtools-mcp section

Browse Source
This commit is contained in:
Petr Baudis
2026-03-13 15:26:38 +01:00
parent 6e03fc4b85
commit 7815f98388
1 changed files with 4 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+4
View File
@@ -48,6 +48,10 @@ scripts/cdp.mjs stop [target] # stop daemon(s)
`<target>` is a unique prefix of the targetId shown by `list`.
## Why not chrome-devtools-mcp?
[chrome-devtools-mcp](https://github.com/ChromeDevTools/chrome-devtools-mcp) reconnects on every command, so Chrome's "Allow debugging" modal can re-appear repeatedly and target enumeration times out with many tabs open. `chrome-cdp` holds one persistent daemon per tab — the modal fires once, and it handles 100+ tabs reliably.
## How it works
Connects directly to Chrome's remote debugging WebSocket — no Puppeteer, no intermediary. On first access to a tab, a lightweight background daemon is spawned that holds the session open. Chrome's "Allow debugging" modal appears once per tab; subsequent commands reuse the daemon silently. Daemons auto-exit after 20 minutes of inactivity.