Proxy and VerifySsl settings in config.yml are ignored by node.js process

Before submitting your bug report

• I've tried finding an answer on the Continue docs site
• I'm not able to find an open issue that reports the same bug
• I've seen the troubleshooting guide on the Continue Docs

Relevant environment info

- OS: WINDOWS 11
- Continue version:
- IntelliJ IDE version: 2022.3.2 Commuity (continue-dev 1.0.33) /2024.3.3 Community (continue-dev 1.0.46)
- Model:
- config:
  

  
  OR link to agent in Continue hub:

Description

i am using the continue plugin in Intellij IDEA. I have configured my config.yml with specific requestOptions including proxy and verifySsl: false to navigate a corporate network with an SSL intercepting proxy. How ever the plugin continues to throw Connection error and PKIX pat building failed errors

Observed Behaviour:

The nodejs backend (Continue) seems to ignore the proxy and verifySsl configurations defined in the config.yml. The Connection only works if i manually set OS-level variables (HTTP_PROXY, HTTPS_PROXY and NODE_TLS_REJECT_UNAUTHORIZED=0) which is not ideal for end user deployment in corporate environments.

Expected Behaviour

Settings defined under requestOptions (specifically proxy and verifySsl) in the config.xml should be passed to the Node.js core process and applied to the underlying HTTP Client used to make LLM requests.

To reproduce

1. Setup a config.tml with a valid apiBase and proxy under requestOptions
2. Set verifySsl: false in request Options
3. Attempt to send a message to the LLM
4. Observe that the connection failes despite the configuration

 requestOptions: 
   verifySsl: false
   proxy: http://<<username:password>@<proxyhost>:<proxyport>

Log output

idea.log shows SSLHandShakeException: PKIX path building failed
core.log shows llm/streamChat: Connection error

Start by tracing how requestOptions from config.yml reach the Node.js core process and the underlying HTTP client, using the reported idea.log and core.log errors to reproduce the failure. Verify the proxy and verifySsl settings are applied to LLM requests; done means the request works without requiring OS-level proxy or TLS environment variables.