Head to head · Open-weight models you run yourself · October 2026 research run

MiMo-V2.6-Flash-RL vs MiniMax-M2.7

MiMo-V2.6-Flash-RL scores 61 (C) on agent readiness against MiniMax-M2.7's 57.6 (C), and leads in every scored category. Both do open-weight models you run yourself.

Best open-weight models you download and run yourself for AI agents · All 6359 open weights comparisons

Which one, for what

MiMo-V2.6-Flash-RL C

Best for Teams with a GPU server, or a provider account, that want an open agent model with a very long context

Ahead on

  • Reach, 65 against 60
  • Risk, 45 against 30
  • Agent interface, 85 against 75
  • Documentation and upkeep, 59 against 42

Watch for

178 GB at 4 bits, so it needs about 200 GB of memory

MiniMax-M2.7 C

Best for Researchers and personal projects with a 4 to 8 GPU server who want an open agent and coding model with parallel tool calls

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

Commercial use needs MiniMax's written authorisation since a licence swap on 11 April 2026, made without a note

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Documentation and upkeep MiMo-V2.6-Flash-RL +17

MiMo-V2.6-Flash-RL 59

Model card 14, Intended use, the architecture, the parameters, the context and the languages (in the metadata) are on the card. Training data 5, A description of the training method with no data sources, sizes or cut-off. Last change 20, the last commits, on 28 October 2026, updated the card, 13 days before this check. Responsiveness 5, Of the 13 most recent discussions that aren't pull requests (21 September to 6 November 2026), 3 have a reply from a XiaomiMiMo member, which is a few. Version policy 5, MiMo-V2.5 stays in its own repositories and V2.6 came out in new ones, with no dated note on the older cards that we read. File health 10, Config, template and card agree on the architecture and the 1M context, and two early faults (invalid JSON in the draft model's config, preprocessor values) were fixed in commits that say so. 14 + 5 + 20 + 5 + 5 + 10 = 59.

MiniMax-M2.7 42

The model card earns 2, stating only intended use and leaving out limitations, architecture, parameters, context, natural languages and a cut-off. Training data earns nothing, since only the training process is described. The last change earns 20, a card commit on 26 October 2026 that renames a MiniMax Agent link to MiniMax Code, 9 days before this check; the files, template and code last changed on 20 April 2026. Responsiveness earns 10, with a MiniMax reply in 8 of 36 discussions, none since June. Version policy earns 5, since earlier and later models sit in their own repositories without dated notes. File health earns 5, because a report that it doesn't load in Transformers v5 waits without a reply.

Risk MiMo-V2.6-Flash-RL +15

MiMo-V2.6-Flash-RL 45

File safety 5, the weights are safetensors, but the dflash folder's mask_embedding.pt is a pickle beside them (15). Provenance 15, the files sit in the XiaomiMiMo organisation, which mimo.xiaomi.com links to per the Distill listing (10). Safety evaluation 0, no safety results on the card. Agent guidance 5, General cautions only. Licence risk 15, MIT has no use policy, threshold or change clause. Security programme 5, Xiaomi runs a company security centre for reporting flaws, as read for the Distill listing (5). 5 + 15 + 0 + 5 + 15 + 5 = 45.

MiniMax-M2.7 30

File safety earns 15, safetensors only with no pickle files, less 10 because every documented loading route passes trust_remote_code for the repository's Python. Provenance earns the full 15, files in the organisation MiniMax links to with a SHA-256 for each shard. Safety evaluation and agent guidance earn nothing, as MiniMax publishes neither. Licence risk earns nothing (read 21 October 2026). The Prohibited Uses appendix goes beyond the law, MiniMax swapped a commercial licence for a non-commercial one two days after release, and neither that swap nor the amendment three days later carries a dated note. The security programme earns nothing, with no security.txt, disclosure policy, SECURITY.md or advisories.

Agent interface MiMo-V2.6-Flash-RL +10

MiMo-V2.6-Flash-RL 85

Chat template 20, chat_template.jinja in the repository (3,868 characters), with a copy in tokenizer_config.json. Tool-calling format 25, the card names the parser to use in two runtimes: the mimo tool-call parser in SGLang and in vLLM, with auto tool choice, and both ship it in a release. Trained tool calling 20, the card describes reinforcement learning on coding and general agent tasks across several harnesses, and the template renders every call in a turn. Structured output 0, Nothing on the card about JSON or schema-constrained output. Reasoning control 10, the template has an enable_thinking switch and keeps reasoning_content, and the card names the mimo reasoning parser for SGLang and vLLM, which returns the reasoning apart from the answer. Context 10, 1M tokens per the card's model summary, and 1,048,576 positions in config.json. 20 + 25 + 20 + 0 + 10 + 10 = 85.

MiniMax-M2.7 75

The chat template earns 20 for chat_template.jinja in the repository. The tool-calling format earns 25, as MiniMax's own guide documents how tools go in and how calls come back, gives a parsing function, and its deployment guides name the vLLM and SGLang parsers. Trained tool calling earns 20, with several invoke blocks in one call. Structured output earns nothing, since JSON output isn't documented or claimed. Reasoning control earns nothing, because thinking is always on with no documented way to turn it off or budget it. Context earns 10 for 204,800 tokens in the config with no position scaling.

Reach MiMo-V2.6-Flash-RL +5

MiMo-V2.6-Flash-RL 65

Memory 5, the smallest build at 4 bits or better is ggml-org's MXFP4 GGUF, 168.93 GB with its projector, and 168.93 GB × 1.2 = 202.7 GB, within 256 GB. Xiaomi's own files are 177.74 GB. ggml-org's Q2_K is below 4 bits and isn't read. Runtimes 20, Released vLLM 0.33.0 and SGLang 0.5.23 have the mimo_v2 model and the mimo parsers, Transformers 5.22.2 has a mimo_v2_flash model, and llama.cpp b12242 has the architecture, with a GGUF from its own organisation. Builds 10, one precision from Xiaomi, the 4-bit files it releases. Terms 15, MIT in the card's metadata, an OSI licence. Download 10, the Hub API reports gated false on 10 November 2026, so the files download with no account and nothing to accept. Hosted 5, the card says it is on Xiaomi's MiMo Open Platform API and on OpenRouter, and Novita is live for it on Hugging Face. 5 + 20 + 10 + 15 + 10 + 5 = 65.

MiniMax-M2.7 60

Memory earns 5. MiniMax only publishes its 230 GB FP8 release, and the smallest build of 4-bit or better from a runtime's own library is LM Studio's Q4_K_M GGUF at 138.3 GB, about 166 GB with the fifth added, so it needs more than our 107.4 GB machine and fits within 256 GB. Runtimes earn the full 25, with model code in released vLLM, SGLang, llama.cpp and Transformers, an LM Studio catalogue entry, and Ollama 0.40.14, whose pinned llama.cpp b11963 has the minimax-m2 architecture (capped at 25). Builds earn 10 for one publisher precision, the FP8 release. Terms earn 5, since the licence today allows only personal, research and non-profit use without MiniMax's written authorisation. Download earns 10, with no gate or account. Hosted earns 5, since Novita, Featherless AI and DeepInfra serve it through Hugging Face, while MiniMax's own API is closed to new users and retires it on 18 November 2026.

Score by category

CategoryWeight this runMiMo-V2.6-Flash-RLMiniMax-M2.7Edge
Capability35%pendingpendingpendingnot scored in this run
Reach25%256560MiMo-V2.6-Flash-RL +5
Risk20%204530MiMo-V2.6-Flash-RL +15
Agent interface10%108575MiMo-V2.6-Flash-RL +10
Documentation and upkeep10%105942MiMo-V2.6-Flash-RL +17
Negative events≤1500
TotalC 61/100C 57.6/100

Facts side by side

FactMiMo-V2.6-Flash-RLMiniMax-M2.7
KindOpen-weight modelOpen-weight model
VendorXiaomi (MiMo team)MiniMax
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceMIT (metadata only, no LICENSE file)MiniMax M2.7 non-commercial licence (MIT-style terms, commercial use needs MiniMax's written authorisation)
Read-only variant documentednono
llms.txtnono
Last release2026-10-282026-04-20
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviewsnone1.8/5 (4)

How the scores have moved

Verdicts

MiMo-V2.6-Flash-RL

A large agent model with an open licence: text, images, video and audio, a 1M context, tool calling it was trained for, and code in four released runtimes. It's a server model, 178 GB at 4 bits, and the card's commands run the repository's code. No safety results, little said about data, and few questions answered.

MiniMax-M2.7

A 230B mixture-of-experts model for coding and agent harnesses, with parallel tool calls, about 200K of context and parsers in vLLM and SGLang. It needs a 4 GPU server for FP8 or about 166 GB for a 4-bit library build, and it always thinks. The main risk is the licence, switched to non-commercial two days after release.

Before you call either

MiMo-V2.6-Flash-RL

  1. Plan for a provider unless you have a multi-GPU server: Xiaomi's API platform, OpenRouter or Novita
  2. On SGLang or vLLM pass --tool-call-parser mimo --reasoning-parser mimo
  3. Use temperature 1.0 and top_p 0.95, as the card recommends
  4. The card's commands pass trust-remote-code. Read the repository's three Python files first, or use Transformers 5.22.2, which has the model built in
  5. Skip the dflash folder unless you need speculative decoding. Its mask_embedding.pt is a pickle
  6. The Use Restrictions section asks for human oversight of high-risk actions

MiniMax-M2.7

  1. Check the use is personal, research or non-profit before starting it; anything commercial needs MiniMax's written authorisation, and commercial users must show Built with MiniMax M2.7
  2. Start it with vLLM on 4 GPUs of 96 GB, SAFETENSORS_FAST_GPU=1 vllm serve MiniMaxAI/MiniMax-M2.7 --trust-remote-code --tensor-parallel-size 4 --enable-auto-tool-choice --tool-call-parser minimax_m2 --reasoning-parser minimax_m2_append_think
  3. In SGLang use --tool-call-parser minimax-m2 and --reasoning-parser minimax-append-think, with --trust-remote-code
  4. MiniMax's guides budget 220 GB for the weights and 240 GB per 1M tokens of KV cache, with 196K the most per sequence
  5. On one large-memory machine, LM Studio's catalogue entry minimax/minimax-m2.7 lists a 138 GB Q4_K_M GGUF and states 138 GB minimum memory
  6. Sample with temperature 1.0, top_p 0.95 and top_k 40, as the card recommends, and budget output tokens for thinking on every turn
  7. Pin Transformers 4.57.1 as MiniMax's guide does; a report that it fails on Transformers v5 has no answer
  8. Without the hardware, call it through Novita, Featherless AI or DeepInfra; MiniMax's own API retires M2.7 on 18 November 2026

Questions

Which is better for AI agents, MiMo-V2.6-Flash-RL or MiniMax-M2.7?

MiMo-V2.6-Flash-RL scores 61 (C) on agent readiness against MiniMax-M2.7's 57.6 (C), and leads in every scored category.

Other comparisons with MiMo-V2.6-Flash-RL or MiniMax-M2.7

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.