VScode插件Codex在wsl中Ubuntu系统超时:Reconnecting，stream disconnected before completion: error sending request for url (https://chatgpt.

I also have the same error on my Macbook.

This error message indicates a networking connectivity issue. Are you able to repro the problem reliably, or is it intermittent?

I solved the problem by forwarding the proxy used by the plugin to my local machine.

I solved the problem by forwarding the proxy used by the plugin to my local machine.

Do you have steps to do that?

> I solved the problem by forwarding the proxy used by the plugin to my local machine. Do you have steps to do that?

我使用"全局代理"模式可以正常使用, 但是PAC模式不行. 大概率还是PAC配置问题.
I can use it normally in 'Global Proxy' mode, but it doesn't work in PAC mode. Most likely, it's still a PAC configuration issue.

This error message indicates a networking connectivity issue. Are you able to repro the problem reliably, or is it intermittent?此错误信息表明网络连接存在问题。您能否稳定重现此问题，还是该问题时有时无？

不好意思，我现在才看到消息，这个是稳定出现的问题，但是我使用的是vscode插件中的codex，在Windows中的wsl2创建的Ubuntu系统，然后ssh远程登录到这个Ubuntu系统会出现这个网络问题，但是通过vscode里面代理目标中转地址为Windows机地址就行了

Translation of previous response to English: Sorry, I only just saw your message. This is an issue that occurs consistently. I’m using Codex through the VS Code plugin, running on an Ubuntu system created in WSL2 on Windows. When I SSH remotely into that Ubuntu system, this network problem occurs. However, it works if I set the proxy target relay address in VS Code to the Windows machine’s address.

OK, so this is a network configuration problem. Thanks for confirming.

OK, so this is a network configuration problem. Thanks for confirming.

你好，我想询问一下，因为网络问题导致收到OpenAI警告，然后plus会员被收回了，我进行申述的话，还能找回吗？

Sorry, I don't know the answer to that. You would need to contact OpenAI customer support.

Sorry, I don't know the answer to that. You would need to contact OpenAI customer support.

好的，感谢您

我的情况是：windows-os可以直接登录codex，并进行聊天。
但是在wsl里面无法登录，也无法聊天。

这确实是网络通讯的问题。
按照这个图片进行配置，并设置为全局代理。

<img width="1052" height="752" alt="Image" src="https://github.com/user-attachments/assets/11ca4cb7-9314-4b89-91ff-8a1a04cfb78f" />

但我需要额外通过在wsl的.bashrc文件中增加如下的代理：
`# 设置 Clash 代理
export http_proxy="http://127.0.0.1:7890"
export https_proxy="http://127.0.0.1:7890"

export no_proxy="localhost,127.0.0.1,::1"`

最终，我通过
curl -I https://chatgpt.com进行测试，如果显示
HTTP/1.1 200 Connection established，就说明是配置成功了

解决了！
我的问题是：User 的 Http: Proxy 和 Remote 的 Http: Proxy 是有冲突的，最初我的 User 是 http://127.0.0.1:7897，在 Remote 中设置成我的 WSL 虚拟网关 IP http://172.28.128.1:7897，这两个同时存在是有冲突的，一直 Reconnecting...
看了楼主的做法直接用 http://172.28.128.1:7897 覆盖 User 原来的 http://127.0.0.1:7897，成功了。如果 User 留空，Remote 设成 http://172.28.128.1:7897，也可以成功，就是不要冲突。
其他前置设置：TUN模式，开启局域网连接，使用 “code .” 从 WSL 打开 vscode

确实就是代理的问题。我本来一直用的是clash for windows（默认端口7890），但最近切换到到了 clash verge（默认端口7897），而vscode的设置中的代理不会自动切换到7897，而是一直都是7890，需要手动切换到7897端口。

Fix: Codex and Claude Code not working in VS Code Remote WSL when VPN is enabled

Context

I was using:

• Windows host
• WSL2
• Ubuntu 26.04 in WSL
• VS Code Remote WSL
• OpenAI Codex CLI / Codex VS Code extension
• Claude Code CLI / Claude Code VS Code extension
• Corporate VPN enabled on Windows

Both Codex and Claude Code worked correctly without the VPN.

As soon as the VPN was enabled, both tools started failing inside WSL / VS Code Remote WSL.

---

Symptoms

Codex error

Codex failed with errors like:

MCP client for `codex_apps` failed to start
HTTP request failed:
error sending request for url (https://chatgpt.com/backend-api/wham/apps)

The Codex conversation could not start properly.

Claude Code error

Claude Code failed with errors like:

ECONNABORTED timeout
Slow first byte: no stream chunk 30.0s after request sent

At first, it looked like an OpenAI / Anthropic / VS Code extension issue, but it was actually caused by WSL2 networking with the VPN.

---

Diagnosis

From Windows PowerShell, with the VPN enabled, the Codex endpoints were reachable:

Invoke-WebRequest -Uri "https://chatgpt.com/backend-api/wham/apps" -Method Head -TimeoutSec 20
Invoke-WebRequest -Uri "https://chatgpt.com/backend-api/codex/responses" -Method Head -TimeoutSec 20

Both returned:

405 Method Not Allowed

This 405 is expected because those endpoints expect POST, not HEAD.

The important part is that Windows could reach the endpoints through the VPN.

However, from WSL2, the tools were failing or timing out when the VPN was enabled.

So the real issue was:

Windows + VPN worked.
WSL2 + default NAT networking + VPN caused Codex / Claude Code traffic to fail.

---

Root cause

The issue was caused by the default WSL2 NAT networking mode interacting badly with the Windows VPN.

With the VPN enabled:

• Windows networking worked.
• WSL2 networking was partially broken.
• Some HTTP/TLS traffic from WSL worked.
• Codex / Claude Code traffic failed or timed out.
• VS Code Remote WSL was affected because the extensions and CLIs were running inside WSL.

The problem was not Codex itself, Claude Code itself, or VS Code itself.

The problem was the WSL2 networking mode.

---

Fix

Create or edit this Windows file:

notepad $env:USERPROFILE\.wslconfig

Add the following configuration:

[wsl2]
networkingMode=mirrored
dnsTunneling=true
firewall=true
autoProxy=true

Then fully restart WSL:

wsl --shutdown
wsl

After restarting WSL, test the Codex endpoints inside WSL:

node -e "fetch('https://chatgpt.com/backend-api/wham/apps').then(r=>console.log(r.status)).catch(console.error)"
node -e "fetch('https://chatgpt.com/backend-api/codex/responses').then(r=>console.log(r.status)).catch(console.error)"

Expected output:

405
405

Again, 405 is fine here. It proves that the endpoints are reachable from WSL.

After enabling WSL2 mirrored networking, both Codex and Claude Code worked again with the VPN enabled.

---

Codex installation note

If codex is not installed inside WSL, install it with npm, not snap.

Check Node and npm:

node -v
npm -v

Install Codex:

sudo npm install -g @openai/codex@latest

Verify:

which codex
codex --version

Then log in and test:

codex login
codex "reply only yes"

Avoid installing Codex with snap in this setup:

sudo snap install codex

In my case, installing Codex through npm worked correctly after fixing WSL networking.

---

Final summary

The issue was:

WSL2 default NAT networking + Windows VPN caused Codex and Claude Code network requests to fail.

The fix was to enable WSL2 mirrored networking:

[wsl2]
networkingMode=mirrored
dnsTunneling=true
firewall=true
autoProxy=true

Then restart WSL:

wsl --shutdown

After switching WSL2 to mirrored networking, WSL used the VPN path correctly and Codex / Claude Code worked again inside VS Code Remote WSL with the VPN enabled.