Remote connection to ChromeOS

[mbhs-josh]

Hi,

ChromeOS includes the Allow remote debugging for this browser instance checkbox on the chrome://inspect/#remote-debugging page.

As expected, when the checkbox is selected, Chrome displays a message indicating remote connections can be made; e.g., Server running at: 127.0.0.1:9222.

Given that it appears that remote connections can be enabled. I'm wondering if it is possible to connect to ChromeOS devices over the network using chrome-devtools-mcp for interaction with the existing browser session?

This would open up some helpful possibilities when it comes to troubleshooting issues that only occur on ChromeOS devices.

Thanks!

[OrKoN]

yes, it should be possible to specify the ws endpoint https://github.com/ChromeDevTools/chrome-devtools-mcp#configuration (--auto-connect flag is not needed as that only connects locally). You might need to do port forwarding on ChromeOS as the server listens on the localhost only.

[mbhs-josh]

Thanks @OrKoN !

I tried to connect a few times using --browserURL and couldn't get it to work. I just tried the --ws-endpoint parameter and it worked straight away.

For the benefit of others who want to do similar. This is how I did it:

Device A = Chromebook that is being connected to remotely.
Device B = Device running chrome-devtools-mcp.

1. Install an SSH server on Device B. Ensure that it allows remote port forwarding, see AllowTcpForwarding.
2. Install the Secure Shell extension on Device A.
3. Open chrome://inspect/#remote-debugging on Device A and enable remote debugging for the browser. Take note of the remote debug port that Device A is listening on.
4. Create an SSH connection from Device A to Device B using the Secure Shell extension. Include the SSH argument that forwards the Device A port (Remote debug port) to Device B. Syntax: -R <Device_B_Port>:127.0.0.1:<Device_A_Port> Example: -R 9222:127.0.0.1:9222
5. Use the --ws-endpoint http://127.0.0.1:<Device_B_Port>/devtools/browser argument when starting chrome-devtools-mcp on Device B.
6. Accept the remote debugging permission prompt on Device A.

Thanks!