Hy3 vs MiMo-V2.6 Distill Qwen 9B

Hy3

Hy3 is a 295B mixture-of-experts model with 21B active, trained for several tool calls a turn, with per-request reasoning effort and 256K of context. It needs an 8-GPU server for FP8 or about 200 GB for a 4-bit build. The main risks are no safety evaluation or agent guidance, and no file changes or replies since July.

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.

Hy3

1. Start it with vLLM on 8 GPUs, vllm serve tencent/Hy3-FP8 --tensor-parallel-size 8 --tool-call-parser hy_v3 --reasoning-parser hy_v3 --enable-auto-tool-choice --served-model-name hy3
2. In SGLang use --tool-call-parser hunyuan --reasoning-parser hunyuan, as the card shows
3. Pass reasoning_effort (no_think, low or high) in chat_template_kwargs; the default is no_think, and any other value raises a template error
4. With the vLLM reasoning parser the chain of thought comes back in message.reasoning and the answer in message.content
5. Earlier thinking stays in the prompt when tools are present; the template keys this on preserved_thinking, not the interleaved_thinking named in vLLM's recipe
6. Use temperature 0.9 and top_p 1.0, the card's recommended sampling
7. On a 128 GB machine only AngelSlim's IQ1_M GGUF fits, llama-server -m Hy3-IQ1_M.gguf -ctk q8_0 -ctv q8_0 -fa on -c 65536, with llama.cpp b11768 or later; at 89.4 GB × 1.2 it sits right at the 107.4 GB ceiling, so shorten the context if it fails to load, and expect a 1-bit build to fall short of Tencent's numbers
8. Without the hardware, call it through Featherless AI or DeepInfra via Hugging Face's inference providers

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