Skip to content

fix(models): accept "responses" as a supported endpoint - #15158

Open
HouMinXi wants to merge 2 commits into
diegosouzapw:release/v3.8.52from
HouMinXi:fix/responses-supported-endpoint
Open

HouMinXi wants to merge 2 commits into
diegosouzapw:release/v3.8.52from
HouMinXi:fix/responses-supported-endpoint

Conversation

@HouMinXi

Copy link
Copy Markdown
Contributor

Summary

Codex model discovery sets supportedEndpoints to ["responses"] for every model it imports (see src/app/api/providers/[id]/models/discovery/codex.ts lines 32, 182, 318). The validation schema in MODEL_SUPPORTED_ENDPOINT_VALUES did not include "responses", so importing any Codex model — including the newly released gpt-6.1-sol — failed with:

Invalid request: supportedEndpoints.0: Invalid option: expected one of "chat"|"embeddings"|...

This adds "responses" to the allowed values. The normalizeModelSupportedEndpoints function passes it through unchanged (no alias mapping needed).

Test plan

  • Existing model-supported-endpoints test suite passes (0 failures)
  • Import gpt-6.1-sol from the Codex GitHub catalog on a live instance and confirm it succeeds

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
HouMinXi force-pushed the fix/responses-supported-endpoint branch from 96489d0 to 707f788 Compare September 30, 2026 05:40
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

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant