timeout waiting for child process to exit
Open 💬 28 comments Opened Jan 28, 2026 by wu-diu-diu
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of Codex is running?
codex-cli 0.92.0
What subscription do you have?
plus
Which model were you using?
gpt5.2
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What terminal emulator and version are you using (if applicable)?
wsl
What issue are you seeing?
thread ID:019c0392-ebfe-7fb1-8aff-f175b8859eb5
What steps can reproduce the bug?
Uploaded thread: 019c0392-ebfe-7fb1-8aff-f175b8859eb5
What is the expected behavior?
_No response_
Additional information
_No response_
28 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
I set the HTTP environment variable in wsl to the proxy opened by the window system, that is, let wsl communicate with the outside world through localhost:8080
me too
me too
@wu-diu-diu, @wangziqi0409, @WayneCYChang, thanks for reporting. Are you on a corporate network/VPN/proxy that you know of? We don't set an explicit timeout ourselves, so trying to see what's terminating the connection.
Me too. I have a good network, but has this error. I restarted, still same.
What server domain should I try to ping?
+1
Version 26.313.41514
VSCode extension
Codex
me too
It's so painful not being able to use CodeX.
me too
It's so painful not being able to use CodeX.
me too
It's so painful not being able to use CodeX.
Having this issue on Windows 11:
codex --version
codex-cli 0.116.0
Having this issue on MacOS
codex --version
codex-cli 0.116.0
This is how I solved it: on macOS, you can enable proxy settings in the Terminal first by exporting your HTTP/HTTPS proxy, and then launch Codex using:
This way, Codex will use the proxy settings you configured before launching.
Note: unfortunately, you need to do this every time you start Codex, which can be a bit tedious.
将代理 换成TUN模式就可以了
Same issue for me on codex-cli 0.117.0, Windows 11, even on brand new Codex launches and brand new sessions. It's pretty much completely unusable right now.
me too
It's so painful not being able to use CodeX.
have to wait until reconnecting 5/5😶
顶,这个方法有用
turn off Tailscale or GoodbyeDPI.
Have tailscale on my machine and have been running into the same issue. This fix worked for me.
Then in your profile use this provider
Same issue. After 5 retries it becomes normal. But sometimes even after 10 retires it still won't work. Can't see what's inside this.
I have searched for solution and I guess if 5 retries make it becomes normal,it's about IPv6;If it still won't work,it may be the sandbox issue.
Please let me use codex qwq
try use this method to set the proxy before open the app, works on my mac:
Many thanks. But what is that "your_proxy" supposed to be? I'm not deliberately setting any proxy 🤯
If you are using a proxy, just use the echo command to see what value is configured on your computer.
If you are not using a proxy, this method isn't for you, and the issue is likely caused by something else.
I got it. I'll try. Many thanks.
This issue is still not fixed on Windows. It has been basically unusable for me. CLI works though. I need the connection to go through proxy.
me too now you find some way?