[BUG] Model list fails to load (ECONNRESET) on remote vscode-server

[vzionv]

Problem (one or two sentences)

The model list cannot be fetched and remains empty. Developer Tools show repeated network errors (ECONNRESET) while fetching models info

Context (who is affected and when)

Happens to users running Roo Code in a remote vscode environment. The issue prevents selecting models because the list never loads.

Reproduction steps

1. Environment/setup
   • OS: CentOS Linux 7 (Linux 3.10.0-1127.el7.x86_64)
   • Roo Code extension: 3.43.0
   • VS Code: 1.108.0
   • Node runtime in Extension Host reports: node 22.21.1
2. Exact actions
   1. Connect to the remote host with VS Code (Remote SSH / vscode-server).
   2. Install/enable Roo Code.
   3. Configure API Provider to OpenRouter.
   4. Open Roo Code model selection list.
3. Observed
   • The model list does not load (empty/unavailable).
   • Extension Host logs show errors fetching OpenRouter models.
   • curl from the same machine can fetch the models successfully, but the extension request fails.

Expected result

The model list loads successfully from OpenRouter and is selectable.

Actual result

The model list fails to load. Extension Host shows ECONNRESET / “Client network socket disconnected before secure TLS connection was established”.

Variations tried (optional)

Confirmed connectivity from the same remote host:

• curl https://openrouter.ai/api/v1/models succeeds.
• Node built-in https.get(...) succeeds (HTTP 200) in the Extension Host environment, while Roo Code’s bundled Axios requests fail with ECONNRESET during TLS setup.

Temporary workaround (works for now):

• Patched/overrode the extension’s bundled Axios instance at runtime so requests use Node’s native http/https transport instead of the bundled Axios adapter.

App Version

v3.43.0

API Provider (optional)

OpenRouter

Model Used (optional)

No response

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

[Extension Host] Error fetching OpenRouter models: {
  "code": "ECONNRESET",
  "message": "Client network socket disconnected before secure TLS connection was established",
  "stack": "Error: Client network socket disconnected before secure TLS connection was established\n\tat Hie.from (~/.vscode-server/extensions/rooveterinaryinc.roo-cline-3.43.0/dist/extension.js:355:15809)\n\tat bE.<anonymous> (~/.vscode-server/extensions/rooveterinaryinc.roo-cline-3.43.0/dist/extension.js:363:11345)\n\tat bE.emit (node:events:519:28)\n\tat $Yt.<computed> (~/.vscode-server/extensions/rooveterinaryinc.roo-cline-3.43.0/dist/extension.js:362:1147)\n\tat ClientRequest.emit (node:events:519:28)\n\tat emitErrorEvent (node:_http_client:107:11)\n\tat TLSSocket.socketErrorListener (node:_http_client:574:5)\n\tat TLSSocket.emit (node:events:519:28)\n\tat emitErrorNT (node:internal/streams/destroy:170:8)\n\tat emitErrorCloseNT (node:internal/streams/destroy:129:3)\n\tat process.processTicksAndRejections (node:internal/process/task_queues:90:21)\n\tat tae.request (~/.vscode-server/extensions/rooveterinaryinc.roo-cline-3.43.0/dist/extension.js:365:2262)\n\tat process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n\tat async fSi (~/.vscode-server/extensions/rooveterinaryinc.roo-cline-3.43.0/dist/extension.js:2917:9229)\n\tat async BRi (~/.vscode-server/extensions/rooveterinaryinc.roo-cline-3.43.0/dist/extension.js:3295:14207)\n\tat async ~/.vscode-server/extensions/rooveterinaryinc.roo-cline-3.43.0/dist/extension.js:3295:16653",
  "name": "Error",
  "config": {}
}

# Node built-in https works (same environment):
node -e "require('https').get('https://openrouter.ai/api/v1/models',r=>{console.log('status',r.statusCode);r.resume()}).on('error',e=>console.error(e))"
status 200

# Attempting to force axios http adapter fails (bundle missing module):
Error: Cannot find module 'axios/lib/adapters/http'

# Attempting to use node build fails (bundle missing file):
Error: Cannot find module 'axios/dist/node/axios.cjs'

[roomote]

I've analyzed this issue and here's my proposed implementation plan:

Root Cause Analysis

The issue occurs because the bundled axios in the extension has TLS connection problems in remote VSCode server environments. The error "Client network socket disconnected before secure TLS connection was established" (ECONNRESET) indicates the socket is being closed during TLS handshake.

The key observation from the issue reporter is that:

• Node's native https.get() works fine on the same machine
• curl works fine
• Only the bundled axios fails

This suggests the bundled axios may be using socket/connection settings that don't work well in certain remote environments (like vscode-server on CentOS).

Proposed Solution

Create a centralized axios instance with explicit httpAgent/httpsAgent configuration that provides more robust connection handling:

1. Create a new utility file src/utils/axiosClient.ts that exports a pre-configured axios instance with:

   • Custom https.Agent with explicit TLS settings
   • Proper keepAlive and socket timeout configuration
   • Fallback to native Node.js http/https behavior

2. Update all API fetchers to use the centralized axios instance:

   • src/api/providers/fetchers/openrouter.ts
   • src/api/providers/fetchers/ollama.ts
   • src/api/providers/fetchers/litellm.ts
   • src/api/providers/fetchers/huggingface.ts
   • And other fetcher files using axios

3. The custom axios configuration will include:

   import https from 'https'
   import http from 'http'
   import axios from 'axios'
   
   const httpsAgent = new https.Agent({
     keepAlive: true,
     timeout: 30000,
     // Ensure proper TLS handling
     rejectUnauthorized: true,
   })
   
   const httpAgent = new http.Agent({
     keepAlive: true,
     timeout: 30000,
   })
   
   export const axiosClient = axios.create({
     httpsAgent,
     httpAgent,
     timeout: 30000,
   })

This approach:

• Explicitly configures connection handling to be more reliable
• Centralizes axios configuration for easier maintenance
• Maintains backwards compatibility
• Should resolve the TLS issues in remote environments by using explicit agents that mirror Node's native behavior

Please mention @roomote in a comment saying that you approve this plan, and I'll proceed with the implementation.