[Windows][26.810.7004] Quick chat accepts a message but never shows a reply

What version of the Codex App are you using (From “About Codex” dialog)?

26.810.7004 (Microsoft Store package OpenAI.Codex_26.810.7004.0_x64)

What subscription do you have?

ChatGPT subscription; exact tier was not collected during local diagnostics.

What platform is your computer?

Windows 11 x64 (Microsoft Windows NT 10.0.26100.0), Simplified Chinese UI

What issue are you seeing?

Quick chat opens normally from the small + button to the right of New chat. The user can type and submit a message, and the user-message bubble remains visible, but no assistant reply ever appears. There is no visible error, spinner, or actionable failure message.

A normal Codex chat created from New chat replies successfully on the same account and network. Fully quitting and reopening the desktop app did not fix Quick chat.

This started after the desktop app updated to 26.810.7004.

A captured failing run showed:

• the Quick chat renderer finished loading;
• chatgpt-account-lookup succeeded with authenticatedAccountPresent=true;
• app routes mounted successfully;
• the failing Quick chat renderer did not subsequently log chatgpt_conversation_updates_subscription_mounted or chatgpt_pubsub_transport_opened, although an earlier Quick chat renderer in the same app session did.

This suggests the Quick chat window can enter a state where it accepts the user message without attaching the conversation-update subscription needed to display the reply.

What steps can reproduce the bug?

1. Open Codex Desktop 26.810.7004 on Windows.
2. Create a normal Codex chat using New chat.
3. Send: Please reply only with OK.
4. Observe that the normal Codex chat replies.
5. Click the small + button to the right of New chat to open Quick chat.
6. Send the same message.
7. Observe that the user bubble appears, but Quick chat remains silent indefinitely.
8. Fully quit Codex Desktop, reopen it, and repeat steps 5–7.
9. Observe the same behavior after restart.

What is the expected behavior?

Quick chat should display the assistant response, or show an actionable error if the request or update subscription fails.

Additional information

• Account lookup succeeds, so this does not appear to be a signed-out state.
• A local HTTP proxy is configured at 127.0.0.1:7897. The proxy is reachable, HTTPS traffic through it succeeds, and normal Codex chats work. The failure is scoped to Quick chat.
• No conversation text, tokens, account identifiers, or raw logs are included in this report.
• Related but not exact reports:
  • #35970 — Quick chat does not work in the merged desktop app on macOS.
  • #35539 — Quick chat returns HTTP 403 on macOS. This Windows case is silent and shows no HTTP error.

Reproduce the failure in the Windows Quick chat renderer using the steps and version above, then inspect the renderer's account lookup and conversation-update subscription events. Compare the failing Quick chat run with a normal chat and the earlier successful Quick chat renderer, focusing on the missing subscription and pubsub events. Done means Quick chat displays the assistant reply or presents an actionable error.