VSCode Extension ignores proxy settings
Resolved 💬 12 comments Opened Aug 30, 2025 by eliotcougar Closed Oct 31, 2025
💡 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.4.0
Which IDE are you using?
VS Code
What platform is your computer?
Microsoft Windows NT 10.0.26100.0 x64
What steps can reproduce the bug?
Trying to use the extension in a restricted environment with a mandatory proxy.
(I know it's a common problem with many VSCode extensions)
What is the expected behavior?
Extension should honor the system-level or VSCode-level proxy settings. Alternatively, the extension can have its own proxy setting.
What do you see instead?
The extension tries to access the Internet directly, and due to restricted nature of our environment, it fails. It basically ignores all proxy settings.
Additional information
_No response_
12 Comments
I've also encountered this issue. I hope to apply the proxy settings of VScode or the system's proxy settings. I'm using MacOS. Are there any plans to resolve this issue? Or are there any other solutions you can provide for reference?
First workaround on Windows is to just use codex-cli in git bash.
Second workaround is to use some app that directs all traffic through a proxy, but acts as a network adapter (VPN). However, that may not work with some restrictive corporate proxies.
I also have this problem, but on Linux. Usually, VSCode extensions use "http.proxy" in settings.json, or "export HTTP_PROXY=..." in the terminal for tools like Claude Code. But Codex ignores all the ways to use a proxy.
Thank you so much for your suggestion! For now, I'm only using Codex CLI or Codex Web/App directly. I'm holding off on using Codex IDE until they fix this issue, then I'll try it again.
A workaround is to hack the codex binary, for remote ssh:
replace
openai.chatgpt-0.4.15with your version andhttp://<your-proxy-host>:<port>with your proxyInspired by your solution but for windows, I made small launcher on C.
This issue appears to be caused by the extension not passing the
http_proxyenvironment variable set in VSCode when calling the codex CLI. Additionally, the current codex does not support settinghttp_proxythrough its own configuration.However, the extension does support setting the path to the codex executable. This feature can be leveraged to create a wrapper script that sets the environment variable before calling codex.
/usr/local/bin/codex-cli-proxyRemember to
chmod +x /usr/local/bin/codex-cli-proxyset -e
export HTTP_PROXY=xxx
export HTTPS_PROXY="$HTTP_PROXY"
exec /usr/local/bin/codex "$@"
After modifying the plugin, it won't open and keeps spinning.
Thanks for the feature request. This will be addressed in the next release.
Proxy works now, but "NO_PROXY" is ignored.
Please clearly say, is VSCode codex Respects the VSCode http-proxy value?
or it's ignoring it?
@steveepreston, this issue was resolved. If you're seeing a related issue with the latest version of Codex, please use the
/feedbackslash command to open a new bug report and provide details and repro steps.