codex - 💡(How to fix) Fix Codex Desktop Stop/checkpoint can lose original thread closeout bubble after continuation [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#17327Fetched 2026-04-11 06:17:38
View on GitHub
Comments
2
Participants
2
Timeline
4
Reactions
0
Timeline (top)
commented ×2labeled ×2

Pressing Stop can preserve the continuation checkpoint but remove the last visible assistant closeout bubble from the original thread.

Root Cause

Pressing Stop can preserve the continuation checkpoint but remove the last visible assistant closeout bubble from the original thread.

RAW_BUFFERClick to expand / collapse

Upstream Bug Report - Codex Desktop Stop/Checkpoint UI Loss

Summary

Pressing Stop can preserve the continuation checkpoint but remove the last visible assistant closeout bubble from the original thread.

Steps to Reproduce

  1. Start a long-running Codex Desktop task in a thread.
  2. While the assistant is still responding or wrapping up, press Stop.
  3. Let Codex create the continuation/checkpoint thread.
  4. Reopen the original thread.
  5. The continuation thread proves the Stop event happened, but the original thread no longer shows the last visible assistant closeout bubble.

Environment

  • macOS
  • Codex Desktop 26.406.31014 (1395)
  • app bundle path: /Applications/Codex.app

Expected

  • The original thread keeps the last visible assistant closeout bubble and the turn closes cleanly.

Actual

  • The continuation thread contains an auto-checkpoint for the same session, but reopening the original thread no longer shows the assistant closeout bubble the operator saw before switching away.

Additional Context

  • This report is based on one historical source thread with operator-corroborated visible content loss after Stop/continuation.
  • A broader local stop-capture dataset shows that raw open-turn-after-stop events are common in proof/probe interruptions and should not be read as bug frequency by themselves.
  • The continuation checkpoint survived; the missing piece is the original thread's visible closeout bubble.

extent analysis

TL;DR

The issue can be mitigated by modifying the Codex Desktop application to preserve the last visible assistant closeout bubble in the original thread when the Stop button is pressed.

Guidance

  • Investigate the Codex Desktop code responsible for handling the Stop button press and checkpoint creation to identify why the last visible assistant closeout bubble is removed from the original thread.
  • Verify that the continuation thread is correctly created and contains the expected auto-checkpoint for the same session.
  • Review the application's thread management and UI update logic to ensure that the original thread's state is properly preserved when the Stop button is pressed.
  • Consider adding logging or debugging statements to track the state of the original thread and the continuation thread when the Stop button is pressed.

Example

No code snippet can be provided without more information about the Codex Desktop application's internal implementation.

Notes

The issue may be related to the application's handling of thread state and UI updates when the Stop button is pressed. Further investigation is needed to determine the root cause of the problem.

Recommendation

Apply a workaround to preserve the last visible assistant closeout bubble in the original thread when the Stop button is pressed, such as modifying the application's thread management and UI update logic. This is recommended because the issue is specific to the Codex Desktop application and a workaround can be implemented without affecting other parts of the system.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING