Feature request: Allow persisting remote debugging permission approval

[domdomegg]

When using --autoConnect with Chrome 144+, every connection attempt shows a permission dialog requiring user approval. It would be helpful to have an option to persist this approval, similar to how USB debugging offers "Always allow from this computer".

Possible solutions:

• A "Remember my choice" checkbox in Chrome's dialog
• A command-line flag to pre-authorize specific clients
• Token-based authentication that persists

[OrKoN]

We have been discussing it a lot. There is no simple solution that also would not allow any program on the machine to easily access your data in Chrome. For now, we recommend to have longer connection sessions to avoid the reconnect dialog. Could you please clarify which clients do you use and why the dialog is causing issues? Does the client often restart the chrome-devtools-mcp server?

[domdomegg]

There is no simple solution that also would not allow any program on the machine to easily access your data in Chrome.

Yeah, it is tricky. Although it should be noted that probably programs on the machine may already be able to do this e.g. by controlling the computer to click the allow button (this is the quite cursed workaround I've been using for now, leveraging https://github.com/domdomegg/computer-use-mcp).

Could you please clarify which clients do you use and why the dialog is causing issues? Does the client often restart the chrome-devtools-mcp server?

Ah I'm using a custom client right now for an personal app I'm developing. The main pain right now is just because I am devving the client, I often need to restart it. And when the client restarts, so does the session to the chrome-devtools-mcp, which means I need to hit allow etc.

But I expect even in usage having to do this for each new session of the client would be somewhat frustrating/frictionful (but probably a lot less frequent!).

[OrKoN]

Compute use is an advanced use case though. The concern here is that with no auth it is easy to extract encrypted state from your regular profile without any indication. With compute use you would probably still see the dialog appearing and being clicked. For development and testing, I'd suggest setting up a dedicated profile for such use cases and running it with --remote-debugging-port=9222 --user-data-dir=/path/to/profile on the Chrome side and --browserUrl=http://127.0.0.1:9222 on the MCP server side. In this case, there will be no dialogs.