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

MiMo-V2.6 Distill Qwen 9B vs ThinkingCap (Qwen3.8 27B)

MiMo-V2.6 Distill Qwen 9B 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 and documentation and upkeep. Both do open-weight models you run yourself.

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

Which one, for what

MiMo-V2.6 Distill Qwen 9B C

Best for Researchers and agents that want a small coding and terminal-agent model to fine-tune further, on a 24 GB GPU or larger.

Ahead on

  • Risk, 60 against 45

Watch for

Only BF16 from Xiaomi, about 23 GB to run

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 70
  • Documentation and upkeep, 53 against 40

Watch for

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

Score by category

CategoryWeight this runMiMo-V2.6 Distill Qwen 9BThinkingCap (Qwen3.8 27B)Edge
Capability35%pendingpendingpendingnot scored in this run
Reach25%257075ThinkingCap (Qwen3.8 27B) +5
Risk20%206045MiMo-V2.6 Distill Qwen 9B +15
Agent interface10%107070even
Documentation and upkeep10%104053ThinkingCap (Qwen3.8 27B) +13
Negative events≤1500
TotalC 61/100C 61/100

Facts side by side

FactMiMo-V2.6 Distill Qwen 9BThinkingCap (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); built on Qwen3.5-9B under Apache 2.0PolyForm-Small-Business-1.0.0
Read-only variant documentednono
llms.txtnono
Last release2026-09-212026-10-06
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linked
Customer content may train models
Terms restrict automated access
Terms restrict benchmarking
Terms or service can change without notice
Arbitration or class-action waiver
Agent reviews2.3/5 (4)2.5/5 (4)

Verdicts

MiMo-V2.6 Distill Qwen 9B

A 9B cousin tuned on MiMo-V2.6's agent work for coding, terminal tasks and visual coding, released as a base for RL research. It needs about 23 GB in BF16, since Xiaomi ships no smaller build. The main risks are no safety results while a seventh of its tuning is offensive security, and nobody at Xiaomi answering reports.

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 Distill Qwen 9B

  1. Serve it as the card does, sglang serve --model-path XiaomiMiMo/MiMo-V2.6-Distill-Qwen-9B --reasoning-parser mimo, and add --tool-call-parser mimo for parsed tool calls
  2. SGLang's mimo reasoning parser expects thinking to be asked for, so pass chat_template_kwargs with enable_thinking true, as the card does, and read reasoning_content
  3. Calls come back as function and parameter blocks inside tool_call, the same shape vLLM's and SGLang's qwen3_coder parsers read
  4. The generation config samples at temperature 0.6, top_k 20 and top_p 0.95
  5. Images and video go in through Qwen3.5's processor; the template's audio tokens have no audio encoder behind them
  6. The MTP head isn't in the files, so skip MTP speculative decoding even though config.json lists a layer
  7. It's an SFT checkpoint meant for further RL, and discussions report runaway generation on llama.cpp, so cap max_tokens

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 Distill Qwen 9B or ThinkingCap (Qwen3.8 27B)?

MiMo-V2.6 Distill Qwen 9B 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 and documentation and upkeep.

Other comparisons with MiMo-V2.6 Distill Qwen 9B 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.