Repository navigation
fix(models): accept "responses" as a supported endpoint - #15158
Merged
diegosouzapw merged 2 commits intoOct 7, 2026
Merged
diegosouzapw merged 2 commits into
diegosouzapw merged 2 commits into
Conversation
4 tasks done
Codex model discovery sets supportedEndpoints to ["responses"] for every model it imports, but the validation schema rejected that value. Adding it to the allowed list lets gpt-6.1-sol and other Codex models import without a schema error. Signed-off-by: Minxi Hou <houminxi@gmail.com>
HouMinXi
force-pushed
the
fix/responses-supported-endpoint
branch
from
September 30, 2026 05:40
96489d0 to
707f788
Compare
TonisOrmisson
added a commit
to TonisOrmisson/OmniRoute
that referenced
this pull request
Sep 30, 2026
Backport upstream diegosouzapw#15158 (707f788). Add a regression through Codex discovery and the import schema. Co-authored-by: Minxi Hou <houminxi@gmail.com>
Co-authored-by: diegosouzapw <8016841+diegosouzapw@users.noreply.github.com>
overbit
added a commit
to overbit/OmniRoute
that referenced
this pull request
Oct 6, 2026
overbit
added a commit
to overbit/OmniRoute
that referenced
this pull request
Oct 6, 2026
overbit
added a commit
to overbit/OmniRoute
that referenced
this pull request
Oct 7, 2026
Allow the "responses" endpoint emitted by Codex model discovery to pass provider model mutation validation instead of failing imports before persistence. Backport the focused fix from upstream diegosouzapw#15158 and add regression coverage using gpt-6.1-sol as the discovered model.
diegosouzapw
merged commit Oct 7, 2026
be7ee7b
into
diegosouzapw:release/v3.8.52
44 of 51 checks passed
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
2 participants
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
Codex model discovery sets
supportedEndpointsto["responses"]for every model it imports (seesrc/app/api/providers/[id]/models/discovery/codex.tslines 32, 182, 318). The validation schema inMODEL_SUPPORTED_ENDPOINT_VALUESdid not include"responses", so importing any Codex model — including the newly releasedgpt-6.1-sol— failed with:This adds
"responses"to the allowed values. ThenormalizeModelSupportedEndpointsfunction passes it through unchanged (no alias mapping needed).Test plan
model-supported-endpointstest suite passes (0 failures)gpt-6.1-solfrom the Codex GitHub catalog on a live instance and confirm it succeeds