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

MiMo-V2.6-Flash-RL vs Qwopus3.8-27B-Flash-V2

MiMo-V2.6-Flash-RL and Qwopus3.8-27B-Flash-V2 score within a point of each other on agent readiness, 61 (C) and 61 (C). Qwopus3.8-27B-Flash-V2 leads on reach and risk. 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

  • Agent interface, 85 against 60
  • Documentation and upkeep, 59 against 51

Watch for

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

Qwopus3.8-27B-Flash-V2 C

Best for Hobbyist and research agents that want a Qwen3.8-27B tuned for shorter reasoning, for local coding loops on a 24 GB GPU.

Ahead on

  • Reach, 85 against 65
  • Risk, 50 against 45

Watch for

Published from a personal account, with no organisation, security contact or safety evaluation

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.

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

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.

Qwopus3.8-27B-Flash-V2 60

Chat template 20, a Jinja file in the repository. Tool-calling format 10 of 25, only the template shows the Hermes-style JSON calls, which differ from the base's format. Trained tool calling 20, several calls a turn. Structured output 0, not documented. Reasoning control 0, the switches are documented but not where the reasoning comes back. Context 10, 262,144 tokens from the base.

Reach Qwopus3.8-27B-Flash-V2 +20

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.

Qwopus3.8-27B-Flash-V2 85

Memory 25 of 30, Jackrong's IQ4_XS GGUF is 15.4 GB, about 18.5 GB with a fifth added, which fits 24 GB. Runtimes 20, it keeps Qwen3.8-27B's architecture, which released vLLM, SGLang, Transformers and llama.cpp run, while Ollama's entry is the base's, not this model's. Builds 15, GGUFs at many precisions from 4-bit to 8-bit and BF16. Terms 15, Apache 2.0 through the chain. Download 10, nothing is gated. Hosted 0, no provider serves it.

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

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.

Qwopus3.8-27B-Flash-V2 51

Model card 11 of 20, missing architecture, context and a cut-off. Training data 5, a description with no cut-off. Last change 15, the files went up on 21 September 2026, 43 days ago, with no commit since. Responsiveness 10, Jackrong answered 2 of 8 discussions across the model's two repositories. Version policy 5, the first Flash release stays up without a dated note. File health 5, no LICENSE file, an experiment note in the template and open reports of looping and a grammar failure.

Risk Qwopus3.8-27B-Flash-V2 +5

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.

Qwopus3.8-27B-Flash-V2 50

File safety 25, safetensors and GGUF only, nothing from the repository runs. Provenance 5 of 15, the files are on a personal account with no site or organisation behind it, though every file has a checksum. Safety evaluation 0, the card says none was done. Agent guidance 5, general cautions about loops and tool reliability. Licence risk 15, plain Apache 2.0. Security programme 0, no contact or policy.

Score by category

CategoryWeight this runMiMo-V2.6-Flash-RLQwopus3.8-27B-Flash-V2Edge
Capability35%pendingpendingpendingnot scored in this run
Reach25%256585Qwopus3.8-27B-Flash-V2 +20
Risk20%204550Qwopus3.8-27B-Flash-V2 +5
Agent interface10%108560MiMo-V2.6-Flash-RL +25
Documentation and upkeep10%105951MiMo-V2.6-Flash-RL +8
Negative events≤1500
TotalC 61/100C 61/100

Facts side by side

FactMiMo-V2.6-Flash-RLQwopus3.8-27B-Flash-V2
KindOpen-weight modelOpen-weight model
VendorXiaomi (MiMo team)Jackrong
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceMIT (metadata only, no LICENSE file)Apache-2.0 (metadata only, no LICENSE file); built on Qwen3.8-27B under Apache 2.0
Read-only variant documentednono
llms.txtnono
Last release2026-10-282026-09-21
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviewsnone2.5/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.

Qwopus3.8-27B-Flash-V2

A Qwen3.8-27B cousin tuned to think less per turn in long agent loops, with an MTP head for speculative decoding in llama.cpp. It fits 24 GB with Jackrong's 4-bit GGUF. The risks are one person's experimental release with no safety work, training traces taken from Claude and GPT, and a tool format that differs from Qwen's.

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

Qwopus3.8-27B-Flash-V2

  1. Quickest start is llama-server -hf Jackrong/Qwopus3.8-27B-Flash-V2-GGUF:Q4_K_M --jinja, about 17 GB, and add mmproj-F32.gguf for images
  2. The card's tests used Q5_K_M with the bundled MTP head and --spec-type draft-mtp in llama.cpp
  3. The template asks for tool calls as JSON inside tool_call tags, so use a Hermes-style parser (vLLM's hermes), not Qwen3.8's qwen3_coder
  4. For coding the card recommends enable_thinking true, reasoning_effort xhigh and temperature 0.3, which you must pass yourself, since generation_config.json says 1.0
  5. reasoning_effort takes xhigh (default), medium or low, and any other value makes the template raise an error
  6. Earlier reasoning stays in the context unless preserve_thinking is false
  7. Cap max_tokens, since a report says it loops more than V1

Questions

Which is better for AI agents, MiMo-V2.6-Flash-RL or Qwopus3.8-27B-Flash-V2?

MiMo-V2.6-Flash-RL and Qwopus3.8-27B-Flash-V2 score within a point of each other on agent readiness, 61 (C) and 61 (C). Qwopus3.8-27B-Flash-V2 leads on reach and risk.

Other comparisons with MiMo-V2.6-Flash-RL or Qwopus3.8-27B-Flash-V2

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.