feat(provider/deepseek): support DeepSeek V4 reasoning effort#14743
Conversation
|
this project is very excellent |
|
Thanks for putting this together — really hoping to see this land soon. We're hitting the same gap on our side: V4 thinking mode is enabled via provider options, but without a way to surface The mapping you chose ( Would be great to get this in a release ahead of the broader V4 model-id work in #14718. Happy to help test against the official endpoint if useful. |
Add DeepSeek provider options for V4 reasoning effort and map the top-level reasoning setting to the OpenAI-compatible reasoning_effort parameter. Document the OpenAI-compatible API boundary and add tests for provider options, top-level mapping, precedence, and disabled thinking.
dancer
force-pushed
the
deepseek-reasoning-effort
branch
from
3952bb5 to
9c05a96
Compare
R-Taneja
added
the
backport
github-actions
Bot
removed
the
backport
|
|
|
🚀 Published in:
|
v6 (provider spec V3) has no top-level `reasoning` parameter, so the top-level mapping logic from #14743 doesn't apply. Keeping only the `providerOptions.deepseek.reasoningEffort` knob.
5 participants
Background
DeepSeek V4 thinking mode supports an OpenAI-compatible
reasoning_effortparameter for controlling thinking strength. The DeepSeek provider already
supports enabling or disabling thinking mode, but it did not expose the new V4
effort control.
Summary
reasoningEffort: 'high' | 'max'to DeepSeek provider options.reasoning_effortin DeepSeek chat completion requests when configured.reasoningsetting to DeepSeek's supported effort values:minimal,low,medium, andhigh->highxhigh->maxprecedence, and disabled thinking.
Manual Verification
N/A - verified with package tests and type checking.
Checklist
pnpm changesetin the project root)Future Work
N/A
Related Issues
N/A