feat: support DeepSeek V4 Flash 0731 - #1364
Merged
Merged
Conversation
Contributor
PR #1364 validation scorecardTitle: feat: support DeepSeek V4 Flash 0731 Verdict: MERGE-SAFE
|
raullenchai
marked this pull request as ready for review
July 31, 2026 18:21
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
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
deepseek-v4-flash-0731-mxfp4alias for the 0731 MXFP4 MLX checkpointWhy
This checkpoint intentionally ships a dedicated encoder and DSML wire format. Without explicit support, Rapid falls back to incompatible ChatML, misloads mixed MXFP4/MXFP8 tensor shapes, and cannot return structured tool calls.
Validation
法国的首都是巴黎)rapid-mlx sharehealth check: ready=true, model_loaded=trueKnown limitation
The community MXFP4 checkpoint answers normal chat correctly, but tool-use quality was unstable in local E2E trials: chat mode declined a requested call and thinking mode repeated
thinkingto the token limit. The official DSML encoding and Rapid parser are covered byte-for-byte/unit/streaming, but this PR does not claim that this particular quantization preserves reliable tool-selection quality.