gpt-oss-120b vs MiMo-V2.6 Distill Qwen 9B

gpt-oss-120b

A reasoning and agent cousin that runs in most runtimes under Apache 2.0 with published safety work. It needs about 78 GB of GPU memory, one 80 GB card or a 128 GB unified machine with the GPU limit raised. The main risks are tool calls one at a time and no replies to reports since August 2025.

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.

gpt-oss-120b

1. Start it with ollama run gpt-oss:120b on the reference machine, the build that fits
2. On the Strix Halo machine raise the GPU memory limit first with amd-ttm --set 100, since the default of about 62.8 GiB is below the 78 GB it needs
3. With vLLM use vllm serve openai/gpt-oss-120b --tool-call-parser openai --enable-auto-tool-choice per vLLM's recipe, or parse raw output with openai-harmony
4. Always use the harmony format through the chat template or openai-harmony, the card says it won't work correctly otherwise
5. Set Reasoning: low in the system message for short tasks, medium is the default
6. Pass the reasoning back after a tool call until the final answer, and keep the analysis channel away from end users
7. Expect one tool call per turn and loop, don't wait for parallel calls

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