Codex Desktop thread stuck in inProgress/interrupted state after clear-log template message

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

26.616.81150

What subscription do you have?

Plus

What platform is your computer?

macOS.

What issue are you seeing?

The original Codex Desktop thread still exists, but it appears stuck. New messages are accepted, yet the chat does not show any response. Its recent runs show as inProgress or interrupted, sometimes with no visible message content.

In plain terms: the conversation is not deleted, but the thread runner/UI seems jammed and can’t resume normally.

What steps can reproduce the bug?

Feedback ID: 019e71fb-99d1-7bd3-845b-2d6ca74fd9dc

What is the expected behavior?

After sending a message in an existing Codex Desktop thread, the thread should continue normally: the message should appear in the conversation, Codex should generate a visible response, and prior links/files/history should remain accessible.

If a message is invalid or unsupported, Codex should show a clear error instead of leaving the thread stuck in an inProgress or interrupted state.

Additional information

The affected thread/session id is 019e71fb-99d1-7bd3-845b-2d6ca74fd9dc.

A separate Codex thread was able to inspect the affected thread and found that it still exists, but recent turns show statuses like inProgress and interrupted. Some recent turns had empty message items.

The original project files still exist locally, so this does not appear to be a filesystem deletion issue. It appears to be a stuck thread/conversation state issue.

The thread contained important project context for an app. I would like to recover/repair the original thread if possible, not just fork or continue in a new session.