Timeout waiting for child process to exit

Open 💬 4 comments Opened Apr 18, 2026 by steven42121

💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex CLI is running?

codex-cli 0.121.0

What subscription do you have?

Timeout waiting for child process to exit

Which model were you using?

Any

What platform is your computer?

Microsoft Windows NT 10.0.26220.0 x64

What terminal emulator and version are you using (if applicable)?

desktop app+VS code...

What issue are you seeing?

Timeout waiting for child process to exit

What steps can reproduce the bug?

Uploaded thread: 019d9f71-1f17-7693-8a9f-d1fc4dd6979b

What is the expected behavior?

I see the problem has been fixed but it still exists in my latest codex app and cli and VS code plugin...

Additional information

_No response_

View original on GitHub ↗

4 Comments

github-actions[bot] contributor · 4 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

#17612
#17779
#17610

Powered by Codex Action

dushaoshuai · 4 months ago

I can reproduce a very similar symptom in the Codex app on macOS: at the start of a new conversation it repeatedly shows Reconnecting... 2/5, 3/5, 4/5, 5/5, and each retry shows timeout waiting for child process to exit, but the turn may eventually succeed afterward.

A workaround that consistently fixed it for me was to create ~/.codex/.env and set proxy environment variables there.

For example, this worked:

https_proxy=http://127.0.0.1:7892
http_proxy=http://127.0.0.1:7892
all_proxy=socks5://127.0.0.1:7892

and in my case even just this was enough:

all_proxy=http://127.0.0.1:7892

After restarting Codex, the repeated reconnect / timeout-at-start behavior stopped.

So this may be useful as a workaround for anyone whose timeout waiting for child process to exit is tied to the startup reconnect loop, especially if their environment is sensitive to proxy / transport routing.

steven42121 · 4 months ago

I just get a copy of .codex folder from my another computer,And I covered the bad one,and...it just work😂

ForceofwiII · 4 months ago

I can reproduce a very similar symptom in the Codex app on macOS: at the start of a new conversation it repeatedly shows Reconnecting... 2/5, 3/5, 4/5, 5/5, and each retry shows timeout waiting for child process to exit, but the turn may eventually succeed afterward. A workaround that consistently fixed it for me was to create ~/.codex/.env and set proxy environment variables there. For example, this worked: https_proxy=http://127.0.0.1:7892 http_proxy=http://127.0.0.1:7892 all_proxy=socks5://127.0.0.1:7892 and in my case even just this was enough: all_proxy=http://127.0.0.1:7892 After restarting Codex, the repeated reconnect / timeout-at-start behavior stopped. So this may be useful as a workaround for anyone whose timeout waiting for child process to exit is tied to the startup reconnect loop, especially if their environment is sensitive to proxy / transport routing.