[codex] Fix automatic Gemini model discovery - #18
Open
222wcnm wants to merge 1 commit into
Open
Conversation
222wcnm
marked this pull request as ready for review
June 27, 2026 14:24
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
This PR fixes automatic Gemini model discovery while preserving OpenAI-compatible model listing behavior.
Changes
/v1beta/modelsrequests to the Gemini API instead of the OpenAI compatibility handler./v1/modelsmodel listing converted to OpenAI-style response objects.keyvalues by selecting one key before proxying.node:testcoverage for Gemini model listing, OpenAI model listing, and query-key selection.Impact
Clients that call the native Gemini model listing endpoint can auto-refresh available models through this proxy, while OpenAI-compatible clients continue to receive the expected
/v1/modelsshape.Validation
node --testNote: Node emits an existing
MODULE_TYPELESS_PACKAGE_JSONwarning becausepackage.jsondoes not declaretype: module; tests pass.