fix: #3268 fix OpenAI Conversations reasoning persistence#3352
Merged
Conversation
This was referenced May 11, 2026
Open
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.
This pull request fixes #3268 OpenAI Conversations session persistence for Responses reasoning items. The SDK now preserves reasoning item server identity when saving to
OpenAIConversationsSession, while continuing to strip stale optional IDs from replayed messages and tool items. It also drops reasoning items that the Conversations API rejects because they have neitheridnorencrypted_content, after advancing the persisted counter so retry and streaming dedupe bookkeeping remains stable.