Repository navigation
Fix connection test efforts and centralize Codex fingerprint settings - #264
Merged
Merged
Conversation
HTExplicit
enabled auto-merge (squash)
October 8, 2026 15:30
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.
Account connection tests currently advertise and send the client-only
ultraworkflow level, and Codex identity configuration is spread across general settings and account forms.This change filters and rejects
ultrabefore test dispatch, adds Extensions → Codex fingerprint for global settings and individual/bulk account modes, and gives the master switch consistent behavior across HTTP, passthrough, WebSocket and credential refresh. Existing seeds and TUI identities remain in place. The protocol fallback is Codex 0.161.0; logical turn IDs, timestamps, window indices and permission metadata are retained. Settings publish immutable per-attempt policies, and stale WS handshakes request a retryable reconnect at the next turn boundary.Validation: targeted native-effort, settings failure/snapshot, identity/lineage/WS compatibility and account handler tests; frontend typecheck, changed-page lint and UI migration/selection tests. Required PR checks remain unchanged. No schema migration or real model request was added. Production config preservation will be checked through the fixed US-only read-only audit after deployment.