Codex occasionally shows mistaken input prompts that do not affect the current task

Open 💬 3 comments Opened Mar 29, 2026 by aisubscriptionshare-debug

What version of Codex CLI is running?

codex-cli 0.117.0

What subscription do you have?

Pro

Which model were you using?

gpt-5.4 xhigh

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

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

PowerShell 7.6.0

What issue are you seeing?

<img width="472" height="167" alt="Image" src="https://github.com/user-attachments/assets/8c03d6ab-8786-49c3-ad71-1f69bb2068a6" />

I have also seen similar messages related to internal failures, such as spawn_agent failing or a required tool not being found. In those cases, Codex still presents an input box as if I need to respond, but my input does not seem to change anything in the ongoing task.

The issue is that these prompts appear to be meaningless or mistaken UI requests. They are confusing because they make it look like Codex is blocked waiting for user input, even though the input seems to have no effect.

What steps can reproduce the bug?

I have seen it appear while Codex is working on a task and an unexpected input prompt is shown. In some cases, the UI also mentions internal issues such as spawn_agent failure or a required tool not being found, but it still presents an input box as if a user response is needed.

What is the expected behavior?

It should not show an input prompt unless user input is actually required and that input will affect the current task. If an internal error occurs, such as an agent failure or missing tool, the UI should report that directly instead of showing a meaningless prompt.

Additional information

None at the moment. I will attach a screenshot as an example.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗