Laguna XS 2.1 vs MiMo-V2.6 Distill Qwen 9B

Laguna XS 2.1

A small coding and agent cousin with 3B active parameters, so it's quick on modest hardware. Poolside's 4-bit GGUF, also Ollama's default, needs about 24 GB, and every major runtime runs it. The main risks are that nobody at Poolside answers its discussions, there are no safety results, and the SGLang route runs repository code.

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.

Laguna XS 2.1

1. Quickest start is ollama run laguna-xs-2.1, 20 GB of files, the same Q4_K_M as Poolside's GGUF
2. On our reference machine use llama-server -hf poolside/Laguna-XS-2.1-GGUF:Q4_K_M --jinja -c 131072, from a llama.cpp release with the laguna architecture (b11772 has it), or BF16 with vLLM (66.9 GB)
3. With vLLM use --tool-call-parser poolside_v1 --reasoning-parser poolside_v1 --enable-auto-tool-choice, on a build with vllm-project/vllm#47311, or --tool-call-parser glm47 on older builds
4. Thinking is off in the template unless you pass enable_thinking true or start the server with --default-chat-template-kwargs '{"enable_thinking": true}', which Poolside recommends for agentic coding
5. Pass earlier reasoning back as reasoning_content in the history, since the card says reasoning may stop in later steps if it's dropped
6. Sampling per the card is temperature 1.0 and top_k 20
7. The card warns that Ollama on Apple Silicon may return empty output until llama.cpp#25389 ships
8. Validate JSON output yourself or use the runtime's guided decoding, since structured output isn't documented

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