Repository navigation
[Windows desktop] Unanswered question card disappears after assistant sends subsequent text #48563
Description
Problem
In the Codex desktop app on Windows, the user repeatedly reports that an unanswered interactive question disappears as soon as the assistant sends another text message after asking it. This makes the selectable answers inaccessible and repeatedly interrupts the workflow.
Steps to reproduce
- In a conversation, have the assistant call
request_user_input_asyncwith a question and two selectable answers. - The tool returns
accepted: true. - Before the user answers, the assistant sends a final text response (for example, explaining that the choice is ready above).
- The user looks for the question card and reports that it is no longer visible.
Expected behavior
An unanswered question and its answer controls should remain visible and actionable after subsequent assistant messages and after turn completion, until it is answered or explicitly dismissed.
Actual behavior
According to repeated user reports in the same conversation, the question disappears when subsequent assistant text is sent. The latest occurrence followed a successful request_user_input_async call immediately followed by a final assistant response. The user explicitly requested this bug report.
Environment and evidence limits
- Windows desktop app, observed/reported on 27 September 2026 (Europe/Amsterdam).
- Exact app build not collected.
- Tool acceptance is visible to the assistant; disappearance is reported by the user. The assistant cannot inspect the native app UI in this session, so the visual root cause is not yet verified.
- No project content, full transcript, credentials, or logs are included.
Impact
Repeatedly prevents the user from answering pending choices. Please check question-card persistence and rendering across assistant text/final messages and turn completion.
Activity
jjansenpio commentedon Oct 1, 2026
Additional occurrence on macOS, submitted at the affected user's explicit request.
Environment:
Behavior:
The user repeatedly reports that pending clickable question/approval prompts disappear, preventing them from answering through the interface. This is not limited to Windows.
Sequence captured in this conversation:
Reissuing earlier questions did allow the user to submit choices once, but the later final-plan approval prompt disappeared again. The exact disappearance trigger is not independently established; subsequent text or turn completion is a plausible reproduction lead, not a confirmed root cause.
Expected: unanswered question controls remain visible and actionable until answered or explicitly dismissed, including after assistant text, turn completion, or switching conversations.
Impact: repeatedly blocks approval workflows and forces the user to ask for the same questions again. The user described the experience as almost making Codex unusable and subsequently moved the ongoing task to another assistant.
Evidence limits: tool acceptance and one successful earlier question submission are confirmed in the conversation; visual disappearance is user-reported. Native app inspection is blocked for agent access, so no UI screenshot or renderer diagnosis was obtained. No private project details, credentials, logs, full transcript, or session identifier are included.
Adombom commentedon Oct 5, 2026
Additional occurrence reported on Windows desktop on 2026-10-04. The affected user explicitly requested that this feedback be sent to OpenAI.
During a conversation with several batches of
request_user_input_asyncquestions, the user repeatedly reported that the question cards disappeared before they could finish answering. The latest batch returnedaccepted: true, then the assistant sent a final response; the next user message reported that the app was wiping the questions while they were answering them. The user had to provide answers manually in the chat instead. The exact UI trigger/root cause has not been independently verified, and the app build was not collected.Please keep pending questions and their answer controls accessible across subsequent assistant messages and turn completion, preserve partially entered answers, and remove them only after submission or explicit dismissal. A way to reopen pending questions would also help.
This report contains no project files, full conversation transcript, credentials or diagnostic logs.
Naaman666 commentedon Oct 15, 2026
Additional occurrence on 2026-10-15, reported at the affected user's explicit request.
Environment measured on the machine: Windows 10 Pro 10.0.19045 x64; installed
codex-cli 0.160.1. The exact running frontend/app build was not independently collected, so the CLI version is not proof of the renderer version.Observed in one conversation:
request_user_input_asyncwith one question and two selectable options. The tool returned{"accepted":true}. The assistant continued other work for several minutes and eventually finished the turn. The user reported that no selection panel appeared.{"accepted":true}. The assistant then sent a final response saying the question was available. The user reported that this panel also did not appear, and said this has happened repeatedly.This corroborates the missing/unanswerable async question symptom here and may also relate to #43753, which was closed with a request for new reports on 0.159.0+. I cannot determine from the available evidence whether the cards never rendered or briefly rendered and were dismissed, nor whether turn completion was the trigger.
accepted:trueis only tool delivery acceptance, not user approval.Expected: the pending question and answer controls remain discoverable and usable until the user answers or explicitly dismisses them; if unsupported, the tool should return an actionable failure or fall back to normal persistent text. This case blocks a required decision in an ongoing coding task.
No private repository names, session identifiers, screenshots, credentials, or raw logs are included.