Flag to force ipv4 on windows
Open 💬 4 comments Opened Apr 4, 2026 by tom-huntington
What version of Codex CLI is running?
codex-cli 0.118.0
What subscription do you have?
pro
Which model were you using?
_No response_
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What terminal emulator and version are you using (if applicable)?
windows terminal
What issue are you seeing?
◦ Reconnecting... 2/5 (35s • esc to interrupt)
└ Timeout waiting for child process to exit
without ipv6 available, codex tries reconnecting 5 times, 30 seconds each attempt, for a total of 2m30s, before proceeding with ipv4.
It does this after each /new command. Totally unusable.
The problem is the Windows API does not handle no ipv6 gracefully, and does a long time out before using ipv4. I have problems with other CLIs in the past, and the solution is just to pass a flag through the cli or use WSL (which works as expected with codex).
I'm on Starlink which has ipv6 problems.
What steps can reproduce the bug?
You would have to disable ipv6 somehow
What is the expected behavior?
_No response_
Additional information
_No response_
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗