Skip to main content

Use Reasoning Behind a Corporate Proxy

Corporate networks often route traffic through a proxy or inspect HTTPS with their own certificate. If Chat shows I couldn't reach the service, or requests fail with certificate errors, configure Reasoning to use the same network path as VS Code.

The extension starts a local Reasoning backend that makes the network requests. These settings are passed to it when it starts, so reload the VS Code window after you change them.

Use the VS Code proxy​

Reasoning follows the VS Code proxy settings. Set them in the VS Code settings, not in Reasoning:

  • http.proxy: the proxy address, for example http://proxy.example.com:8080;
  • http.noProxy: hosts that should bypass the proxy.

When http.proxySupport is off, Reasoning ignores any proxy, including HTTP_PROXY and HTTPS_PROXY set in your shell.

Trust your company certificate​

By default, Reasoning trusts the certificates in your operating system's trust store, as VS Code does. When the proxy inspects HTTPS with a certificate that is not in that store:

  1. Get the company's root certificate as a PEM file from your IT team.
  2. Open the VS Code settings and set ai-cockpit-reasoning.extraCaCerts to the file's absolute path, for example C:\certs\company-root.pem or /etc/ssl/company-root.pem.
  3. Reload the VS Code window.

Certificate verification​

If VS Code's http.proxyStrictSSL is set to false, Reasoning also skips certificate verification, matching VS Code. This removes an important protection; prefer adding the company certificate instead.

If requests still fail, select Details on the error in Chat and share the technical information with your IT team. See Understand Chat errors.