3 ms·

> unlike chrome-devtools-mcp which starts a fresh headless instance each time I'm pretty sure chrome-devtools-mcp can connect to a running instance: https://de

by xnx 1y ago

> unlike chrome-devtools-mcp which starts a fresh headless instance each time I'm pretty sure chrome-devtools-mcp can connect to a running instance: https://developer.chrome.com/docs/devtools/remote-debugging/local-server https://developer.chrome.com/docs/devtools/remote-debugging/...

felarof 1y ago
Hmm I've tried. Google chrome doesn't allow starting `--remote-debugging-port` on main profiles. Logs below from my MacOS. not sure if it allows on other OSes. ``` [I] ~ /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --enable-logging=stderr --remote-debugging-port=9445 (base) [27920:145785320:1017/131556.797325:INFO:components/enterprise/browser/controller/chrome_browser_cloud_management_controller.cc:206] No machine level policy manager exists. DevTools remote debugging requires a non-default data directory. Specify this using --user-data-dir. ```
deleted 1y ago
[deleted]