Disable use of tool_choice=required for deepseek-reasoner
#3644
Conversation
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
ZeroAurora
changed the title
Contributor
Author
|
The test is a false positive I think |
DouweM
changed the title
tool_choice=required for deepseek-reasoner
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.
I've been experimenting with DeepSeek v3.2 recently, and find the reasoner model from the official endpoint yields 400 Bad Request when
openai_supports_tool_choice_requiredis not set to False. That is, deepseek-reasoner does not supporttool_choice=required, at least for now.I'm not sure if it's a provider-specific issue or a model characteristic, so I'm changing the provider side.