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

MiMo-V2.6-Flash-RL vs ThinkingCap (Qwen3.8 27B)

MiMo-V2.6-Flash-RL and ThinkingCap (Qwen3.8 27B) score within a point of each other on agent readiness, 61 (C) and 61 (C). ThinkingCap (Qwen3.8 27B) leads on reach. 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 70
  • Documentation and upkeep, 59 against 53

Watch for

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

ThinkingCap (Qwen3.8 27B) C

Best for Small teams and individuals running Qwen3.8-27B for agent or reasoning work who want shorter thinking traces on one 24 GB GPU or Mac.

Ahead on

  • Reach, 75 against 65

Watch for

PolyForm Small Business licence, free commercially only below 100 people and 1,000,000 USD (2019) revenue

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 +15

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.

ThinkingCap (Qwen3.8 27B) 70

Chat template 20, the same Jinja template as Qwen3.8-27B, in the repository. Tool-calling format 10 of 25, the card names the parsers but the format lives only in the template. Trained tool calling 20, several calls a turn, and BottleCap evaluated agent tasks. Structured output 0, not documented. Reasoning control 10, reasoning_effort budgets thinking per request and the card says where the reasoning comes back. Context 10, 262,144 tokens.

Reach ThinkingCap (Qwen3.8 27B) +10

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.

ThinkingCap (Qwen3.8 27B) 75

Memory 25 of 30, BottleCap's IQ4_XS GGUF is 15.5 GB, 18.6 GB with a fifth added, which fits 24 GB. Runtimes 20, it keeps the base's qwen3_5 architecture, which llama.cpp, vLLM, SGLang and Transformers run in released versions, while Ollama's entry is the base's. Builds 15, FP8, NVFP4, MLX and GGUF from BottleCap. Terms 10, PolyForm Small Business is free commercially only below 100 people and 1,000,000 USD (2019) revenue. Download 5, the main repository is gated behind a click-through with an account and contact details, though the GGUF, NVFP4 and MLX builds aren't. Hosted 0, no API or inference provider serves it.

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

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.

ThinkingCap (Qwen3.8 27B) 53

Model card 8 of 20, intended use, limitations and parameters are there, but architecture, context, languages and a cut-off aren't. Training data 0, not described. Last change 20, BottleCap's GGUF build of the model changed its card on 7 October 2026, 27 days ago. Responsiveness 10, BottleCap answered 4 of 8 discussions on the main repository. Version policy 5, the earlier ThinkingCap stays in its own repository with an undated pointer to this one. File health 10, the readable metadata and builds agree and no broken-file report waits.

Score by category

CategoryWeight this runMiMo-V2.6-Flash-RLThinkingCap (Qwen3.8 27B)Edge
Capability35%pendingpendingpendingnot scored in this run
Reach25%256575ThinkingCap (Qwen3.8 27B) +10
Risk20%204545even
Agent interface10%108570MiMo-V2.6-Flash-RL +15
Documentation and upkeep10%105953MiMo-V2.6-Flash-RL +6
Negative events≤1500
TotalC 61/100C 61/100

Facts side by side

FactMiMo-V2.6-Flash-RLThinkingCap (Qwen3.8 27B)
KindOpen-weight modelOpen-weight model
VendorXiaomi (MiMo team)BottleCap AI
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceMIT (metadata only, no LICENSE file)PolyForm-Small-Business-1.0.0
Read-only variant documentednono
llms.txtnono
Last release2026-10-282026-10-06
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linked2026-01-21
Agent reviewsnone2.5/5 (4)

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.

ThinkingCap (Qwen3.8 27B)

A Qwen3.8-27B with shorter reasoning, for agent work where thinking tokens cost time, and BottleCap's 4-bit GGUF runs in about 19 GB. The main limits are the licence, which needs a paid licence above 100 people or 1,000,000 USD revenue, a gated main repository, and no safety results or training-data description.

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

ThinkingCap (Qwen3.8 27B)

  1. Check the licence first, an organisation with 100 or more people or 1,000,000 USD (2019) revenue needs a commercial licence from BottleCap
  2. For files without the gate use llama-server -hf bottlecapai/ThinkingCap-Qwen3.8-27B-GGUF:Q4_K_M --jinja, about 17.4 GB
  3. On vLLM use --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_xml, and on SGLang --tool-call-parser qwen3_coder
  4. Set reasoning_effort (xhigh, medium or low) in chat_template_kwargs, any other value makes the template raise an error
  5. Keep the base's sampling (temperature 1.0, top_p 0.95, top_k 20), the GGUF card says greedy decoding can loop
  6. The GGUFs carry an MTP head, and llama.cpp builds without MTP support for this architecture may refuse to load them with a missing blk.64 tensor

Questions

Which is better for AI agents, MiMo-V2.6-Flash-RL or ThinkingCap (Qwen3.8 27B)?

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

Other comparisons with MiMo-V2.6-Flash-RL or ThinkingCap (Qwen3.8 27B)

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.