Mistral Large 4 vs Swift 1.5 Qwen3.8-Flash-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.

Swift 1.5 Qwen3.8-Flash-Next

A large mixture-of-experts cousin, Qwen3.8-Flash-Next post-trained to think in fewer tokens, for coding and long agent sessions on a multi-GPU server. Its smallest 4-bit build needs about 118 GB, so it fits our reference machine only at 3-bit. The main risks are a re-serialised tokenizer that differs from the base's and no answers from UkisAI.

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

Swift 1.5 Qwen3.8-Flash-Next

1. On a multi-GPU node use vllm serve ukisai/Swift1.5-Qwen3.8-Flash-Next --tensor-parallel-size 8 --max-model-len 262144 --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder, the parser the base's recipes and the card's SGLang command use
2. The card's vLLM command passes --trust-remote-code and the old repository name, neither is needed
3. On our reference machine only UkisAI's GSQ-RCO IQ3_S GGUF (84.7 GB with the projector) fits, below 4-bit
4. Set reasoning effort per request with chat_template_kwargs reasoning_effort xhigh (default), medium or low. UkisAI's own runs lose about 2.5 points at medium and low
5. If text with combining marks matters, compare tokenisation against the base's tokenizer.json before trusting outputs
6. Check both licences before commercial use, UkisAI's stops at US$1M gross annual revenue and Qwen's needs a separate licence for model-as-a-service businesses