Repository navigation
fix: preserve Codex conversations with verified strict device transport - #288
Merged
Merged
Conversation
added 11 commits
October 15, 2026 11:12
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.
Codex fingerprint modes previously collapsed independent conversations and account tests could report a configured identity without sending it. This change keeps one persistent credential-source device while preserving independently scoped root/child/fork conversations, canonical metadata and real execution diagnostics. Legacy session/full values remain readable and take effect as device mode without rewriting stored identities or adding migrations.
Enabled simulation now requires a verified in-process transport for HTTP, WS, credential refresh and model catalogs. Profiles are pinned to official Codex 0.162.1 (092d3acd), with unsupported versions/plugins reported explicitly and uncertain transport outcomes blocked from replay or generic-client fallback. The UI exposes verified/pending versions, strict profiles and actual test identity/TLS observations.
Validation: focused identity/namespace/shadow/test/WS, TLS trust, cancellation, proxy, streaming and no-replay cases; affected frontend typecheck, lint and 12 view tests. Native Windows, Linux and both macOS architectures were captured with isolated custom CAs against loopback only (sample run 38678469179). Actual implementation TLS, H2 settings/flow/header order, H1 order/spelling and WS offers matched the reference. No real model requests were made. Normal required PR checks remain enabled.