[macOS][Chat] Completed final answer is absent below “Worked for” despite sidebar preview; File → New Window restores it #52204

Summary

In the unified ChatGPT/Codex macOS desktop app, ordinary Chat mode intermittently fails to render the entire final assistant response in the currently open conversation window. The sidebar preview may already contain the beginning of the generated final answer, but selecting that conversation shows only the Worked for … activity/thinking section. The final-answer region below that section is completely absent.

Opening File → New Window and navigating to the same conversation immediately restores the normal view: Worked for … followed by the complete final answer. No application restart is needed.

Important distinction: This is not the final response being rendered inside the Worked for section. Expanding that section shows the expected interim commentary, tools/search activity, and status. The separate final response itself is missing from the affected window.

Environment

• App: Unified ChatGPT/Codex desktop app on macOS, regular Chat mode (not a local Codex task or Quick Chat floating window).
• Desktop client version: 26.1002.52244, reported by the session's desktop client identifier; exact About-dialog build number not independently checked.
• Platform: macOS, Apple Silicon (exact OS version not collected).
• Subscription: ChatGPT Pro.
• Observed: October 8, 2026.
• Frequency: Intermittent, recurring across conversations; not claimed to be deterministic.

Steps / observed sequence

1. Open or continue an ordinary Chat-mode conversation in the macOS desktop app.
2. Send a prompt and wait while the assistant generates a response.
3. The conversation's sidebar preview can show the beginning of the generated answer.
4. Select/open that conversation in the current window. The view displays Worked for … and its proper activity, but no final response below it.
5. Expanding/collapsing Worked for … does not reveal the final answer: it contains distinct interim content, not the final answer.
6. Without quitting the app, choose File → New Window and reopen the same conversation there.
7. The full final answer now appears beneath Worked for …, as expected.

The reporter confirmed step 6–7 resolves the problem. Restarting the application has also recovered the content but is impractical when concurrent long-running Codex tasks are active.

Expected vs. actual

Expected: Once a response is completed, the current Chat view renders its final assistant message below the completed Worked for section, consistent with the sidebar preview and persisted conversation. Switching back to a conversation should not hide the finished answer.

Actual: The final answer is completely missing from the active window's message display, even though the sidebar preview has shown it. The separate working/activity section renders correctly. A freshly opened window loads and displays the missing answer.

This suggests a window-local rendering/conversation-state synchronization problem, but no root cause has been verified. No claim that the response was deleted or that its contents were reclassified into the activity section.

Impact and workaround

This interrupts routine Chat use and makes successfully completed responses look empty. Repeated full restarts are especially costly/risky for a user running long-lived Codex tasks at the same time.

Non-destructive workaround confirmed: File → New Window, then open the affected conversation in that new window. It restores the response without closing/restarting the app.

The reporter has screenshots of the recovered state in both collapsed and expanded Worked for views showing the final answer properly below the activity. A screenshot of the missing-answer state was not captured for this report; no private conversation screenshot is attached publicly.

Related reports (similar symptoms, distinct surfaces/recovery)

• Windows app: conversations appear hung after agent completion; replies surface only after reopening / Could not load messages #49062 (Windows desktop): Completed responses are invisible until conversation reopen; that report also describes hangs and a Couldn't load messages error. The macOS incident here has no such observed loading error and is reliably restored by a new app window.
• [macOS] Quick Chat omits completed final answers and stays on thinking/search activity after reopening history #51919 (macOS Quick Chat): On the same 26.1002.52244 desktop version, the floating Quick Chat surface shows activity without a completed answer. This report concerns ordinary Chat in the main application window, with a confirmed New Window recovery.
• Final response is incorrectly placed inside the Thinking/“Worked for” section, leaving no visible output #41948 (previously closed): Describes final content being grouped inside Worked for. Here the working section contains different, appropriate progress content, and the separate final answer is wholly absent from the broken window.

Please evaluate whether these share a desktop message-projection/window-state cause while keeping the distinct UI behavior and recovery paths visible.