[Docs] Clarify DeepSeek Flash image support - #60
Draft
zoomote[bot] wants to merge 1 commit into
Draft
Conversation
7 tasks
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
1 participant
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.
What changed
The DeepSeek provider guide now identifies
deepseek-flashas the multimodal model for image attachments, explains that the retired Flash IDs are temporary aliases, and notes thatdeepseek-v4-prodoes not accept images.Why this change was made
DeepSeek's current API contract changed with the September 10 V4.1 release, while the provider guide still referenced retired chat and reasoner models and gave no image-selection guidance.
Impact
Users are directed to the correct current model for screenshot, diagram, and other visual analysis instead of manually overriding capabilities.
Related PRs