Repository navigation
Keep Codex transcripts exact-once after Stop - #472
Merged
Merged
Conversation
cfal
force-pushed
the
fix-dupe
branch
2 times, most recently
from
August 5, 2026 13:16
b387ebc to
559df51
Compare
cfal
force-pushed
the
fix-dupe
branch
2 times, most recently
from
August 5, 2026 14:05
fc4d905 to
c2b219a
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
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.
Codex Stop followed by a new message could leave both provider-native and retained-live copies of the same turn in the canonical transcript. This aligns recovery coverage with Codex 0.146.0 and carries exact request and turn-item identities across live delivery so native reconciliation replaces matching retained rows without ever treating equal message text as identity; no migration is required because the wire shape is unchanged.