Codex desktop: Interactive question options disappear before the user can respond
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.908.40834
What subscription do you have?
Pro
What platform is your computer?
macOS, Codex desktop app
What issue are you seeing?
The assistant displayed two interactive multiple-choice questions at once. Before I finished reading the questions and options, they disappeared automatically. I had not selected an option, submitted an answer, or dismissed the questions, leaving me unable to respond.
What steps can reproduce the bug?
- The assistant called request_user_input_async with two multiple-choice questions.
- The tool returned {"accepted":true}, and the questions and options appeared in the UI.
- The assistant then sent a final response, ending its turn.
- The question options disappeared before the user answered.
What is the expected behavior?
Unanswered questions should remain available until the user submits an answer or explicitly dismisses them. If the assistant ends its turn, the app should preserve a way to respond or allow the questions to be reopened from the conversation. A missing response must not be treated as acceptance of a default option.
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue in the Codex desktop app on macOS using request_user_input_async with two multiple-choice questions, then let the assistant end its turn. Trace the question lifecycle from tool acceptance through the final response; done means unanswered options remain available until submission or explicit dismissal and are not treated as accepted defaults.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, rust
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100