Chrome DevTools Protocol CLI - zero dependencies.
chmod +x chrome-ws./chrome-ws start # Launch Chrome (auto-detects platform)
./chrome-ws new "https://example.com" # Create tab
./chrome-ws navigate 0 "https://example.com"
./chrome-ws extract 0 "h1" # Extract headingSKILL.md- Complete usage guideEXAMPLES.md- Real-world examples
./test-raw.sh # Raw JSON-RPC
./test-tabs.sh # Tab management
./test-navigate.sh # Navigation
./test-interact.sh # Form interaction
./test-extract.sh # Content extraction
./test-wait.sh # Wait commands
./test-e2e.sh # End-to-end workflow
./test-host-override.js # Smoke test for host/port overrides- Node.js 16+
- Chrome with
--remote-debugging-port=9222
- The CLI now binds to
127.0.0.1:9222by default to avoid name-resolution issues on Windows. - Customize the connection via
CHROME_WS_HOST/CHROME_WS_PORTif you forward DevTools elsewhere.