fix(server,web): hide first-message retractions immediately - #28
Merged
Merged
Conversation
github-actions
Bot
added
vouch:trusted
asfires
force-pushed
the
t3code/first-message-retraction-cleanup
branch
from
August 13, 2026 17:42
ca0c6e4 to
4e7125f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Retracting the first message already deletes the new T3 thread, but provider settlement could leave its temporary sidebar row visible until cleanup finished, and Codex retained the discarded native thread in its own history.
Hide first-message recovery threads from thread-discovery surfaces immediately, restoring them automatically if recovery fails. Cancelled sends restore and delete immediately; claimed sends follow normal start-and-interrupt settlement before restoring and emitting the existing reverted-and-deleted event pair.
After that durable first-message retraction deletion—and only that deletion—the provider cleanup requests an optional transient-thread discard before ordinary session shutdown. Codex implements the capability with its native
thread/deleteoperation; unsupported providers such as Claude no-op. Failures are best-effort and never block T3 deletion or session cleanup. Mid-thread retractions and ordinary thread deletion are unchanged.Implemented by GPT-5.6-Sol through the Codex harness.