http.proxy is configured in VSCODE, connecting to IBMi through code for IBM i from our extension not possible when already connected to GitHub using Github Copilot

In our extension MDOpen for MDCMS 8.6.x we use code for IBM i extension using connectionData with nickname, host, userid, pw, sshport

const connectionData: ConnectionData = {
name: nickname,
host: host,
username: userid,
password: pw,
keepaliveInterval: keepaliveInterval,
port: sshport,
};

ibmConnected = await **vscode.commands.executeCommand(`code-for-ibmi.connectDirect`, connectionData);**

if (ibmConnected) { ...

now we have users of our extension they have http.proxy configured in VSCode settings they need to access their AI models apparently with GitHub Copilot extension (https://marketplace.visualstudio.com/items?itemName=GitHub.copilot-chat).

So they are not able to connect any more through our extension to IBMi. Even though it's through SSH. Should not be affected by a http.proxy setting.

But if they add their local IP addresses of their IBMi servers to the NO Proxy settings in VSCODE then it works again as expected.

Do you have any idea what could be the cause of this? Do you have any similar experiences why that happesn?

Thanks for your support.

Start with the code-for-ibmi.connectDirect command and the connectionData path shown in the report, then compare its SSH connection behavior with VS Code's http.proxy and no-proxy settings. Reproduce the failure with http.proxy configured and an IBM i host omitted from no-proxy. Done means the cause is identified and the extension can connect as expected without requiring users to add each server to no-proxy.

Written by the indexing model from the issue text.