According to this documentation: https://github.com/mongodb-js/devtools-shared/blob/1fd9027d29718f9bcf31c4fc0bb517aa9df1b5ac/packages/devtools-proxy-support/src/proxy-options.ts#L117-L127

Electron does not support either SSH proxies or authenticated proxies. It means that, when a user configures the proxy and restart the application, they get locked out of Compass and can't fix the configuration unless they edit the internal configuration file.

A small fix has been already released to give a more friendly error message to the user when this happens: https://jira.mongodb.org/browse/COMPASS-8345 .

Now what we want to do is:

• Disable the SSH proxy configuration entirely, hiding it, from Compass.
• Disable username and password in HTTP/HTTPS proxy, by hiding these fields and living them empty.

After COMPASS-8382, Compass now informs the users that Electron's own resource fetching (e.g. HTML img tag sources, intercom scripts, etc.) won't be using the proxy. If we want to fix this, we'd need to implement a solution similar to the one described in the linked code, where we'd open a proxy on localhost that forwards through the intended proxy, and somehow (this is the hard part) ensure that other applications on the same machine wouldn't be able to use that localhost proxy.