Ling-3.0-tiny vs Qwen3.8-Flash-Next

Ling-3.0-tiny

A small, quick hybrid reasoning cousin for local agent work, tool calls and coding, under MIT. It runs in about 6 GB from inclusionAI's 4-bit GGUF in released Transformers, vLLM, SGLang and llama.cpp, with no host. The main risks are a card that doesn't match the files in places, the vLLM route running repository code, and no model safety results.

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.

Ling-3.0-tiny

1. Start it with llama-server -hf inclusionAI/Ling-3.0-tiny-GGUF:Q4_K_M --jinja -c 32768, which needs llama.cpp b11772 or a recent release with bailingmoe3
2. With vLLM 0.32.0, vllm serve inclusionAI/Ling-3.0-tiny --trust-remote-code --enable-prefix-caching --mamba-cache-mode align --enable-auto-tool-choice --tool-call-parser ling3 --reasoning-parser ling3, which runs the repository's config code
3. With SGLang 0.5.22, its cookbook uses --reasoning-parser deepseek-r1 --tool-call-parser glm45 for this model, and drop the card's NEXTN flags since tiny has no MTP layer
4. Thinking is on by default, pass chat_template_kwargs with enable_thinking false for short tasks
5. Sampling per the card is temperature 1.0, top_p 0.95 and top_k 20
6. The template keeps earlier reasoning in the prompt, which grows long agent sessions
7. Validate JSON output yourself or use the runtime's guided decoding, since structured output isn't documented
8. For a guardrail, inclusionAI's Ling-3.0-tiny-singprobe scores intent, unsafe output and hallucination per token, but only through SGLang and vLLM integration branches

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