Nanbeige4.3-33B vs Qwen3.8-Flash-Next

Nanbeige4.3-33B

A dense 33B Llama-architecture cousin for long agentic coding and office tasks, with per-request thinking, XML tool calls that stock vLLM and SGLang parse, and 512K of context. It needs about 96 GB at BF16, as Nanbeige ships no quantised build. Its agentic results so far are Nanbeige's own, with no safety results, training data notes or licence file.

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.

Nanbeige4.3-33B

1. Serve with vllm serve Nanbeige/Nanbeige4.3-33B --enable-auto-tool-choice --reasoning-parser qwen3 --tool-call-parser qwen3_coder, as the card says, or SGLang with the same two parsers
2. Keep tool_call_format at its default xml, since qwen3_coder parses that format; the json option writes Hermes-style JSON calls, which need a different parser such as vLLM's hermes
3. Pass chat_template_kwargs {"preserve_thinking": true} for multi-turn tool use and coding, and {"enable_thinking": false} to skip reasoning, as the card recommends
4. Use temperature 1.0, top_p 0.95 and up to 65,536 new tokens for agent work, and temperature 0.6 for reasoning and chat, per the card
5. Send your own system prompt, since without one the template injects a Chinese identity line, or a Chinese tool-expert prompt when tools are passed
6. Send one system message at the start only, as the template raises an error for a later one
7. In plain Transformers pass use_cache=True to generate, since config.json and generation_config.json set it false; trust_remote_code isn't needed

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