Skip to content

Fix DeepSeek V4.1 reasoning effort catalog - #37

Merged
theFong merged 1 commit into
theFong:mainfrom
razorback4417:fix/deepseek-v41-reasoning-efforts
Oct 4, 2026
Merged

theFong merged 1 commit into
theFong:mainfrom
razorback4417:fix/deepseek-v41-reasoning-efforts

Conversation

@razorback4417

Copy link
Copy Markdown
Contributor

deepseek-v4.1-flash rejects medium, but setup currently advertises low/medium/high for every Webster model and defaults to medium. That leaves Codex selecting an effort the backend won't accept.

This adds one catalog override for V4.1:

  • default: high
  • supported: low, high, xhigh, max

All other discovered models keep the current low/medium/high profile, and the proxy still forwards requests unchanged.

I kept this in catalog generation because Webster's /v1/models response doesn't expose reasoning capabilities. We shouldn't need an entry for every new model—only models whose contract differs from the shared default. If Webster starts returning capability metadata, that should replace the local overrides.

Tested with the proxy suite and the repository test suite.

@theFong
theFong merged commit 6fe37b0 into theFong:main Oct 4, 2026
1 check passed
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.

2 participants