Support NO_PROXY / http.noProxy settings in VSCode Extension

Resolved 💬 5 comments Opened Jan 16, 2026 by gaby Closed Mar 7, 2026

💡 Likely answer: A maintainer (etraut-openai, contributor) responded on this thread — see the highlighted reply below.

What version of the VS Code extension are you using?

0.5.60

What subscription do you have?

Plus and Copilot

Which IDE are you using?

VS Code

What platform is your computer?

Ubuntu 24.04

What issue are you seeing?

When using a proxy, we want the requests going to our API gateway go through without a proxy. Other IDe's like continue.dev, cline, kilo respect the http.noProxy setting from VSCode, but Codex doesn't.

https://smallzero.github.io/programming/2025/07/30/added-proxy-in-vscode.html

What steps can reproduce the bug?

Add NO_PROXY and the extension ignores this and sends the request to that host through the proxy.

What is the expected behavior?

NO_PROXY is respected by the extension.

Additional information

_No response_

View original on GitHub ↗

5 Comments

reoLantern · 7 months ago

Also worth noting: this doesn’t seem limited to the VS Code extension. The Codex CLI also appears to ignore NO_PROXY / no_proxy — requests to hosts that should bypass the proxy are still routed through it. It would be great if both the extension and CLI could consistently respect NO_PROXY / no_proxy (and http.noProxy where applicable).

etraut-openai contributor · 5 months ago

This feature request hasn't received any upvotes, so I'm going to close it.

gaby · 5 months ago

@etraut-openai What do you mean??? We are waiting for openai to fix it.

etraut-openai contributor · 5 months ago

@gaby, we prioritize feature requests based on community upvotes. If a feature request doesn't get enough upvotes, it is closed. There are hundreds of other feature requests that the community has upvoted, so that's where we'll focus our time and attention.

gaby · 5 months ago

@etraut-openai Thanks, I will keep using claude then.