CLI becomes unresponsive
Open 💬 2 comments Opened May 10, 2026 by toolMan-tang
💡 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.130.0
What subscription do you have?
plus
Which model were you using?
5.4
What platform is your computer?
window
What terminal emulator and version are you using (if applicable)?
window cmd
What issue are you seeing?
会话窗口，不能接受数据结果；不能停止，不能输入文本，一直卡着；只能关闭；发现两种结果：上个任务已经成功完成，结果能看到；另一种是中断；一个任务对话完成后，再次任务必现；在window进行修改，读取文件等；给了最高权限；一直卡着，至少二十分钟以上没有任何反馈；重复之前提过的问题
What steps can reproduce the bug?
Uploaded thread: 019dfc2b-4646-73a1-a169-a3292c8934a1
What is the expected behavior?
_No response_
Additional information
_No response_
2 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
English translation:
Title: Serious bug in Codex Windows CLI
What version of Codex CLI is running?
codex-cli 0.130.0
What subscription do you have?
Plus
Which model were you using?
5.4
What platform is your computer?
Windows
What terminal emulator and version are you using, if applicable?
Windows cmd
What issue are you seeing?
The conversation window cannot receive result data. It cannot be stopped, and I cannot enter text. It remains stuck, and the only option is to close it.
I observed two outcomes:
After one task conversation completes, the issue reproduces every time on the next task.
This happens when modifying files, reading files, etc. on Windows. I granted the highest permissions. It remains stuck with no feedback for at least 20 minutes.
This is a repeat of a previously reported issue.
What steps can reproduce the bug?
Uploaded thread:
019dfc2b-4646-73a1-a169-a3292c8934a1What is the expected behavior?
No response
Additional information
No response