Qwen3.5-2B vs Qwen3.8-Flash-Next

Qwen3.5-2B

A small vision-language cousin for prototypes, fine-tuning and light local steps such as tool calls, tagging or reading an image, running in about 2 GB at 4 bits in every major runtime under plain Apache 2.0. Keep thinking off, since the card warns it loops. The main risk is neglect, with no safety results or answers from Alibaba since March.

Qwen3.8-Flash-Next

A large sparse cousin with 6B active parameters for agentic coding and multimodal work, previewing Qwen's next architecture. It needs a 128 GB Mac for Ollama's MLX build or about 144 GB for the 4-bit GGUF, and Qwen Cloud serves it. The main risk is a licence that needs a separate deal for hosted-model and coding or office assistant businesses.

Qwen3.5-2B

1. Smallest start is ollama run qwen3.5:2b-q4_K_M (1.9 GB); plain qwen3.5:2b pulls the 2.7 GB Q8_0 build
2. Full precision vllm serve Qwen/Qwen3.5-2B --port 8000 --max-model-len 262144 --enable-auto-tool-choice --tool-call-parser qwen3_coder
3. Thinking is off by default; if you turn it on with "chat_template_kwargs": {"enable_thinking": true}, stream and cut off runaway output, since the card warns of thinking loops, and add --reasoning-parser qwen3 in vLLM or SGLang to split the reasoning out
4. There's no generation_config.json, so pass the card's sampling yourself, for example temperature=1.0, top_p=1.0, top_k=20, presence_penalty=2.0 for text without thinking
5. Use it for narrow steps or as a fine-tuning base, not as the main agent, as the card itself suggests
6. Validate any JSON it returns, since structured output isn't documented

Qwen3.8-Flash-Next

1. On a 128 GB Mac start it with ollama run qwen3.8-flash-next:125b-mlx (105 GB, NVFP4), on Linux the smallest Ollama build is qwen3.8-flash-next:125b-a6b-q4_K_M at 120 GB, which won't fit a 107.4 GB GPU share
2. On a server, vllm serve Qwen/Qwen3.8-Flash-Next-FP8 --tensor-parallel-size 4 --max-model-len 262144 --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder
3. Use the qwen3_coder tool parser and the qwen3 reasoning parser, as Qwen's GitHub README does
4. Thinking is on by default, pass chat_template_kwargs with enable_thinking false to skip it, and read the reasoning from reasoning_content, even though SGLang's cookbook says thinking can't be turned off
5. reasoning_effort takes xhigh (default), medium or low, and any other value makes the template raise an error
6. Send at most one system message and put it first, since the template raises an error otherwise
7. Sampling per the card is temperature 1.0 and top_p 0.95 when thinking, temperature 0.7, top_p 0.8 and presence_penalty 1.5 without
8. vLLM keeps the 51B n-gram table in host memory on 80 GB GPUs by default, per its recipe
9. Validate JSON output yourself or use the runtime's guided decoding, since structured output isn't documented
10. Read the Qwen Community License before serving it to others as an API or inside a coding or office assistant product