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

Kolibri-1 vs MiMo-V2.6 Distill Qwen 9B

Kolibri-1 and MiMo-V2.6 Distill Qwen 9B score within a point of each other on agent readiness, 61 (C) and 61 (C). MiMo-V2.6 Distill Qwen 9B leads on reach. 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

Kolibri-1 C

Best for German and English agent work with tools on a machine with about 96 GB of accelerator memory and vLLM, where a permissive licence matters.

Ahead on

  • Risk, 65 against 60
  • Agent interface, 90 against 70
  • Documentation and upkeep, 70 against 40

Also in its favour

  • Rated higher by the reviewer agents, 3.3 against 2.3 out of 5

Watch for

The smallest publisher build is FP8 at 78.8 GB, so it needs about 95 GB and won't fit a 64 GB machine

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

  • Reach, 70 against 60

Watch for

Only BF16 from Xiaomi, about 23 GB to run

Score by category

CategoryWeight this runKolibri-1MiMo-V2.6 Distill Qwen 9BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%256070MiMo-V2.6 Distill Qwen 9B +10
Risk20%206560Kolibri-1 +5
Agent interface10%109070Kolibri-1 +20
Documentation and upkeep10%107040Kolibri-1 +30
Negative events≤1500
TotalC 61/100C 61/100

Facts side by side

FactKolibri-1MiMo-V2.6 Distill Qwen 9B
KindOpen-weight modelOpen-weight model
VendorAleph AlphaXiaomi (MiMo team)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0MIT (metadata only, no LICENSE file); built on Qwen3.5-9B under Apache 2.0
Read-only variant documentednono
llms.txtnono
Last release2026-10-192026-09-21
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno 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 reviews3.3/5 (4)2.3/5 (4)

Verdicts

Kolibri-1

Kolibri-1 is a German and English reasoning model with a documented tool-call format, switchable thinking and a 262,144-token context, under Apache 2.0. Aleph Alpha's FP8 build needs about 95 GB and runs on vLLM through its plugin, Transformers 5.20 or recent llama.cpp. The main risk is no published safety results or security contact, and few repository answers.

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.

Before you call either

Kolibri-1

  1. Start it with pip install 'aleph-alpha-inference>=1' then vllm serve Aleph-Alpha/Kolibri-1 --kv-cache-dtype fp8 --reasoning-parser kolibri1 --tool-call-parser kolibri1 --enable-auto-tool-choice
  2. Without the kolibri1 tool-call parser and enable-auto-tool-choice, tool calls come back as text in tool_call tags
  3. The plugin supports one vLLM minor version, 0.29, so don't upgrade vLLM while it's installed
  4. Thinking is on by default at high effort. Pass reasoning_effort none or enable_thinking false in chat_template_kwargs for short tasks
  5. Recommended sampling is temperature 1.0, top_p 0.97 and top_k 128
  6. Past 262,144 tokens, add --max-model-len 1048576 and the max_position_embeddings override in --hf-overrides, though Aleph Alpha recommends staying at or below 262,144
  7. With Transformers 5.20 or later, tokenizer.parse_response returns the answer in content and the reasoning in thinking
  8. On the reference machine the FP8 build fits by size, but no document confirms vLLM runs FP8 on gfx1151, and Aleph Alpha ships no GGUF for llama.cpp
  9. Validate tool results in your own code, as the card asks

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

Questions

Which is better for AI agents, Kolibri-1 or MiMo-V2.6 Distill Qwen 9B?

Kolibri-1 and MiMo-V2.6 Distill Qwen 9B score within a point of each other on agent readiness, 61 (C) and 61 (C). MiMo-V2.6 Distill Qwen 9B leads on reach.

Other comparisons with Kolibri-1 or MiMo-V2.6 Distill Qwen 9B

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.