feat(responses): add encrypted reasoning replay opt-in - #9601
Closed
jackjinke wants to merge 0 commit into
Closed
Conversation
This was referenced Aug 6, 2026
jackjinke
force-pushed
the
feat/encrypted-reasoning-replay-recreated
branch
3 times, most recently
from
August 8, 2026 13:37
717c14a to
934153d
Compare
Owner
|
Thanks for the PR. Please address the mandatory items (tests and/or merge blockers) in this branch, then rerun checks before /merge-prs. |
3 similar comments
Owner
|
Thanks for the PR. Please address the mandatory items (tests and/or merge blockers) in this branch, then rerun checks before /merge-prs. |
Owner
|
Thanks for the PR. Please address the mandatory items (tests and/or merge blockers) in this branch, then rerun checks before /merge-prs. |
Owner
|
Thanks for the PR. Please address the mandatory items (tests and/or merge blockers) in this branch, then rerun checks before /merge-prs. |
Owner
|
Obrigado pelo PR. Mantive a revisão de
|
diegosouzapw
force-pushed
the
feat/encrypted-reasoning-replay-recreated
branch
from
August 11, 2026 01:10
934153d to
5fd2325
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.
Summary
reasoning.encrypted_contentinput items when enabledencrypted_contentvalues from persisted structured payloads and captured SSE chunks while retaining compact diagnostic markersRecreates #9004, which was accidentally closed and could not be reopened.
Closes #9000
Tests
Test files included from the original PR:
tests/unit/chatcore-translation-paths.test.tstests/unit/strip-reasoning-blobs-agentic-context-1599.test.tstests/unit/provider-specific-data-schema.test.tstests/unit/request-defaults-store-session.test.tstests/unit/request-log-payloads.test.tstests/unit/ui/edit-connection-modal-free-models.test.tsxThe original PR's validation and coverage details remain available in #9004.
Manual combo validation
Validated one session against a combo containing
gpt-5.6-solandkimi-k3:gpt-5.6-sol; encrypted reasoning content was returned and preserved in client replay history.gpt-5.6-solfrom the combo; the same session switched tokimi-k3and continued successfully. OmniRoute omitted the Codex-only encrypted reasoning item from the non-Responses upstream request while the client retained it.gpt-5.6-sol; the same session switched back and continued successfully with the retained encrypted reasoning available again.This confirms mixed-provider combo switching does not break the session and Codex encrypted reasoning survives a temporary hop through a non-Responses target for reuse when routing returns to Codex.
Context
Inspired by OpenAI's report that retained reasoning and compaction tripled ARC-AGI-3 scores while reducing output tokens: https://openai.com/index/how-two-settings-tripled-our-arc-agi-3-scores/
This PR intentionally adds only user-controlled passthrough for encrypted reasoning already present in request input. It adds no replay cache, stored-response lineage, or server-side compaction policy.