Earlier quoted context omitted.
Could you go into a bit more detail about this? Why is exposing devtools to the agent a problem? What's the attack vector? That the agent might do something malicious to exfil saved passwords?
Forget the agent, browser-use's published setup instructions to use with your own Chrome profile and passwords [ https://docs.browser-use.com/customize/real-browser , https://github.com/browser-use/browser-use/blob/495714e2dd38... ] launches a Chrome session with Remote Debugging enabled. These tools they are guiding users to setup and execute are "inherently insecure" [ https://issues.chromium.org/issues/40056642 ].…
I would surmise that this will stop being a problem if you switch to using a unix socket for the CDP.