Codex desktop: pending question interface disappears after switching tabs and does not return
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?
Version 26.901.31953
What subscription do you have?
Pro
What platform is your computer?
macOS 26.6.2, Codex desktop app.
What issue are you seeing?
A pending structured user-input question disappears when the user switches tabs and does not reappear on return. The user cannot continue answering the original question through its interface.
What steps can reproduce the bug?
User-reported sequence (not independently reproduced):
- In a Codex desktop conversation, have the assistant ask a question using
request_user_input_async. - While the question is pending, switch tabs.
- Return to the conversation.
- The question interface is gone and does not reappear.
The exact tab type and whether assistant completion affects this behavior have not yet been isolated. Reissuing the question restored an opportunity to answer in this conversation.
What is the expected behavior?
Unanswered questions should remain recoverable in their originating conversation after tab switching, with their pending state and any entered answers preserved until submitted or explicitly dismissed.
Additional information
This report is submitted at the affected user's request. No private conversation, logs, or project content are included. Related issue #32458 concerns timed auto-dismissal in the VS Code extension; this report concerns tab switching in the macOS desktop app, without a confirmed timer.
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
Start by reproducing the sequence in the Codex desktop app using request_user_input_async: leave a question pending, switch tabs, and return. Trace the pending question through the tab switch and verify whether its state and entered answers are retained. Done means the originating conversation still shows the unanswered question until it is submitted or dismissed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, rust
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100