Windows desktop: user-visible progress/commentary disappears from durable task transcript

Summary

In the Codex Windows desktop app, a progress/commentary message can be visible and read during an active response, then disappear after the response completes or the activity collapses. This creates a gap between what the user experienced and what remains in the durable task transcript.

OpenAI Support case: 14017561

Environment

• OpenAI.Codex 26.825.5331.0
• Windows 11 personal PC
• Incident: August 30, 2026, America/Los_Angeles

Example

This progress message was visible and read:

I’m opening the continuous ledger at the repaired section and verifying the marker sequence once more before showing you the exact control.

After finalization or interface collapse, it was no longer recoverable in the durable transcript.

Steps to reproduce

1. Open a Codex task in the Windows desktop app.
2. Request work that produces visible progress/commentary before the final answer.
3. Read and note one visible progress message.
4. Allow the response to finish or activity to collapse.
5. Review the durable transcript.
6. Observe whether that progress text is missing.

Expected behavior

Every user-visible assistant message should remain recoverable in the durable chronological transcript or an export, including streamed progress/commentary.

Actual behavior

Some visible progress/commentary disappears after finalization or interface collapse, so the retained transcript may not fully represent the experienced conversation.

Impact

This interferes with chronological reconstruction, correction auditing, accessibility, and user trust.

ILRL lineage backing

An append-only Innovation Lineage Record Live (ILRL) record preserved: (1) the visible statement being read; (2) its disappearance from the durable transcript; (3) a separately marked recovery receipt; and (4) escalation to OpenAI Support.

Local lineage coordinates are D3.414 for the recovered incident and D3.423 for the support-escalation receipt. They are declared record references—not platform-issued identifiers or proof of immutable storage—and document only the observed interaction sequence.

This does not ask OpenAI to endorse ILRL; it identifies the recordkeeping method that exposed the continuity defect.

Privacy

No private project archive, GOOPE material, credentials, or unrelated personal files are included.

No source file, test, or entry point is identified in the issue. Start by reproducing the missing progress/commentary in the Windows desktop app, then trace how streamed messages are finalized and written to the durable transcript or export. Done means every user-visible assistant message remains recoverable after completion or activity collapse.