Mistral Large 4 vs Qwen3-Coder-Next

Mistral Large 4

A frontier-sized open cousin for coding agents and defensive security, with strict JSON Schema output, parallel tool calls and three reasoning efforts. It needs a multi-GPU server, about 732 GB for the smallest 4-bit build, and vLLM and SGLang run it only from special images. The main risk is a licence that bars Model-as-a-Service businesses without a separate deal.

Qwen3-Coder-Next

A fast coding cousin for agent harnesses, with 3B active parameters and tool calling trained across many scaffold formats for Claude Code, Cline or Qwen Code loops. Alibaba's 4-bit GGUF needs about 58 GB, fitting one 64 GB machine, and two providers host it. The main risk is neglect, with no change since February, no replies and no safety results.

Mistral Large 4

1. Serve the NVFP4 build on Blackwell with vllm/vllm-openai:mistral-large-4 --model mistralai/Mistral-Large-4-1T-A52B-NVFP4 --tensor-parallel-size 8 --kv-cache-dtype fp8_ds_mla --tool-call-parser mistral --reasoning-parser mistral --enable-auto-tool-choice; released vLLM doesn't load it
2. On H200 use the FP8 build with tensor parallelism of 16 or 8 by 2 pipelines, per vLLM's recipe
3. Pass reasoning_effort low, medium or high (default high); any other value makes the template raise an error, and there is no off switch
4. Read the reasoning from message.reasoning; max_completion_tokens counts reasoning tokens too
5. Use temperature 1.0 and top_p 0.95 at every effort, per the card
6. Ask for JSON with response_format type json_schema and strict true; the template passes the schema to the model
7. The template rejects a tool message straight after a user message and a conversation that doesn't start with a user or system message
8. Add --speculative-config '{"method": "dspark", "num_speculative_tokens": 3}' to use the embedded draft head
9. If you'll offer it to others as a hosted model, read the licence first; Model-as-a-Service use needs Mistral's commercial licence

Qwen3-Coder-Next

1. Quickest start is ollama run qwen3-coder-next (Q4_K_M, 52 GB of files)
2. On our reference machine Alibaba's Q8_0 GGUF (84.8 GB, about 102 GB in use) also fits, run with llama-server -m Qwen3-Coder-Next-Q8_0/Qwen3-Coder-Next-Q8_0-00001-of-00004.gguf --jinja -ngl 99 -fa on -c 131072
3. Serve with vllm serve Qwen/Qwen3-Coder-Next --enable-auto-tool-choice --tool-call-parser qwen3_coder (vLLM 0.15.0 or later), using the built-in parser rather than the repository's qwen3coder_tool_parser_vllm.py, which fails to import on newer vLLM per discussion 36
4. The card's commands use tensor parallel 2 though the text says 4 GPUs, and it suggests cutting the context to 32,768 if the server fails to start
5. There's no thinking mode, so don't pass enable_thinking or wait for reasoning_content
6. Sampling per the card is temperature 1.0, top_p 0.95 and top_k 40
7. The GGUF card's llama.cpp example path omits the quant from the file name; the real files are named like Qwen3-Coder-Next-Q4_K_M-00001-of-00004.gguf
8. Validate any JSON it returns, since structured output isn't documented