Codex desktop thread history is not persisted and task remains permanently in progress

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

26.825.51511

What subscription do you have?

Pro

What platform is your computer?

macOS Tahoe 26.5.1 - Darwin 25.5.0 arm64 arm

What issue are you seeing?

Summary

A Codex desktop task appears to lose its conversation history after the initial user prompt and first assistant response. A background task remains marked as inProgress, while subsequent conversation and work are not visible when viewing the thread.

A previous task exhibited the same behavior, and the current thread appears affected as well.

The UI also shows:

You stopped after 0s

The background task may remain permanently marked as inProgress, despite no longer being active. This creates a mismatch between the visible conversation, task status, and any work performed through external tools or durable coordination systems.

Impact

• Conversation context is lost from the user-facing thread.
• The task cannot be reliably resumed from the UI.
• Task status becomes misleading or permanently stuck.
• Long-running agent workflows may continue or make progress without that history being visible.
• Users may need to recover context from external logs, handoffs, or project state.

Evidence

Attached screenshot showing the initial prompt, the first assistant response, and the You stopped after 0s state.

Additional observations

A prior Codex task in the same workflow displayed similar behavior: its original turn remained permanently inProgress, while later conversation was not persisted.

### What steps can reproduce the bug?

1. Start a Codex desktop task
2. Reopen or inspect the thread from the desktop application.

### What is the expected behavior?

## Expected behavior

The complete conversation should remain visible and the thread status should accurately reflect whether a task is running, stopped, completed, or failed.

## Actual behavior

Only the initial user prompt and the first assistant response are visible. Later conversation turns are missing from the thread.

### Additional information
https://github.com/user-attachments/assets/f23dbbed-71de-4593-9d23-20112eb37f2b

Start by reproducing the issue in the Codex desktop application using the listed steps, then trace where thread history and task status are persisted. Done means all conversation turns remain visible after reopening or inspecting a thread, and its status accurately reflects whether it is running, stopped, completed, or failed.