fix: enable image input for MiniMax-M3 - #166
Open
octo-patch wants to merge 1 commit into
Open
Conversation
wangtsiao
force-pushed
the
main
branch
2 times, most recently
from
July 30, 2026 05:39
e2b0d84 to
a91dc66
Compare
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.
Reason: MiniMax-M3 is cataloged as text-only in the built-in model catalog although the model supports image input and Devo already supports image attachments end to end.
Changes:
imageto theinput_modalitiesof theMiniMax-M3built-in model entry incrates/core/models.json.builtin_minimax_m3_supports_image_input) asserting MiniMax-M3 advertises image input.Checks:
cargo fmt --all -- --checkcargo test -p devo-core model_catalog