octocode-chrome-devtools

Launch Chrome with open-browser.mjs on a CDP port, then run the network-measure-check script through cdp-sandbox.mjs against that port. It emits a health score plus JSON findings you can filter with measure-query, and deeper captures use live-har-monitor or HAR paging.

Capture traffic with the live-har-monitor or network-body-har-fetch checks, then page the resulting .har file with har-pager using filters like --filter failures or --status. Redact secrets with har-redact before sharing, and ingest bodies into a scrape corpus to prove API fields locally.

Node.js 22 or later is required because the runner relies on the native WebSocket client. The sandboxed runner's --allow-net network scoping additionally requires Node 25+, since earlier versions grant network access under the permission model.

Yes, via the cookie-bridge script, which transfers cookies from an existing CDP session, a Playwright storage-state file, or a real profile into an isolated session. It requires explicit approval with --i-understand-secrets and never prints cookie values.

Use static crawling for site maps, bulk extraction, and pages whose content is available without JavaScript execution. The CDP approach is for live evidence like network failures, console errors, and interactions; thin JS shells should be handed to the scraping workflow.

Most failures come from calling a method before enabling its domain, routing commands to the wrong session, or stale API assumptions across Chrome versions. Enable domains like Page, Runtime, and Network before listeners, and check /json/protocol for locally supported methods.