fix: use Codex account runtime in connectivity tests - #970
Merged
Merged
Conversation
Co-Authored-By: Codex <noreply@openai.com>
Merged
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.
The Admin connectivity test for GPT-6.1 Sol sent Codex client version
0.0.0, while normal routing used the configured version and account catalog. Remote reproduced the upstream HTTP 400 before this change.The shared OAuth account client builder now loads the existing account-scoped Codex runtime for probes, preserving client version, persisted account/FedRAMP identity, proxy, and model metadata. The test still targets one account and does not use routing fallback or write request telemetry.
Validation: two real Admin-endpoint regression cases failed on version
0.0.0before the fix and pass afterward (default and overridden client versions, account identity, Responses Lite, streaming greeting, and no telemetry). All 79 focused tests, Gateway typecheck, Biome, and diff checks pass.No configuration or database migration is required. Release and Remote deployment will follow full CI acceptance.