Answered question cards still appear pending on Windows desktop after phone reply #53489

What version of the Codex App are you using?

Installed Windows package metadata: OpenAI.Codex 26.1007.2314.0, read locally. The About-dialog display version and phone app version were not collected. Observed on October 12, 2026.

What platform is your computer?

Windows desktop, with the same Codex conversation accessed from a phone. Phone OS and app version were not collected.

What issue are you seeing?

I reported answering an assistant question from my phone, but its question card remained visible and actionable in the desktop app.

In the observed conversation, the assistant received the submitted answer, acted on it, and finished the task. A later desktop screenshot still showed the original question card, its suggested responses, and the Send update control. The stale card makes a completed request look as though it still needs an answer.

What steps can reproduce the bug?

Observed workflow; a controlled clean-session reproduction has not been performed:

1. Have Codex ask a question using its interactive question UI.
2. Open the same conversation on a phone and submit an answer.
3. Confirm that the assistant receives the answer and continues the task.
4. Return to the conversation in the Windows desktop app.
5. Observe that the answered question card remains visible as an apparently pending request, even after the assistant completes the task.

What is the expected behavior?

Submitting an answer on the phone should mark that question as answered across devices and automatically dismiss the pending question card on desktop. The answer should remain in conversation history, without requiring a second submission or manual dismissal.

Additional information

Evidence: phone submission is user-reported; structured answer delivery is directly visible in the conversation; desktop card persistence is shown in the user-provided screenshot. The question used request_user_input_async. Its answer reached the assistant as a structured question-reply message associated with the original question, rather than an unrelated ordinary chat message. A client synchronization or stale UI-state problem is a hypothesis, not an established root cause. Frequency and behavior after restarting or reopening the desktop app have not been tested.

Related but distinct: #44648 reports stale async questions in the CLI after an answer in normal chat. This report concerns a structured reply submitted on mobile and an answered card persisting on Windows desktop; a common cause is unconfirmed.

Prepared with AI assistance at my request. No screenshots, private conversation identifiers, raw logs, project files, or credentials are attached.