[BUG] When in an HTTP proxy environment, MCPs and modes cannot be retrieved

[44010083]

Problem (one or two sentences)

RemoteConfigLoader.ts:91 uses axios, which requires configuring httpsAgent or httpAgent to work properly in an HTTP proxy environment.

Context (who is affected and when)

When users in an HTTP proxy environment open the Roo Marketplace page, the page displays "No marketplace items found."
No marketplace items found.jpg

Reproduction steps

1.win10
2.click "Marketplace"

Expected result

show marketplace items

Actual result

No marketplace items found.

Variations tried (optional)

No response

App Version

v3.38.3

API Provider (optional)

None

Model Used (optional)

No response

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

[roomote]

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

Problem: RemoteConfigLoader.ts uses axios without proxy configuration, causing marketplace requests to fail when users are behind an HTTP proxy.

Proposed Solution:

1. Add https-proxy-agent as a dependency in src/package.json - this is the standard library for creating proxy agents that work with Node.js http/https modules

2. Create a utility function getHttpsProxyAgent() in a new file src/utils/proxyAgent.ts that:

   • Reads VSCode's proxy settings via vscode.workspace.getConfiguration("http").get<string>("proxy")
   • Falls back to environment variables (HTTPS_PROXY, HTTP_PROXY)
   • Returns an HttpsProxyAgent instance if a proxy is configured, or undefined otherwise

3. Modify RemoteConfigLoader.ts to:

   • Import the proxy agent utility
   • Pass the httpsAgent option to axios requests in fetchWithRetry()

This approach:

• Respects VSCode's built-in HTTP proxy settings that users configure in their settings
• Falls back to standard environment variables for compatibility
• Only creates the agent when needed, keeping the code efficient
• Follows the pattern recommended for VSCode extensions

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

[mrubens]

@44010083 does this seem right to you? Should Roomote try / would you be able to test it out?

[44010083]

@mrubens using fetch in VS Code extensions is more elegant,because fetch automatically respects VS Code's http.proxy settings, eliminating the need to manually configure an httpAgent with axios.
const response = await fetch(url);
return response.text as T

[44010083]

@mrubens using fetch in VS Code extensions is more elegant,because fetch automatically respects VS Code's http.proxy settings, eliminating the need to manually configure an httpAgent with axios. const response = await fetch(url); return response.text as T

The code, modified based on v3.38.3, has successfully passed the tests

[hannesrudolph]

@roomote give it a go!

[roomote]

I've seen this issue and will implement the fix using the native fetch API as suggested by @44010083, since fetch automatically respects VS Code's http.proxy settings. I'll open a PR to share progress shortly.