Darwin-36B-Opus vs MiniMax-M3.1-Flash

Darwin-36B-Opus

A text-only reasoning cousin merged from Qwen3.6-35B-A3B and a reasoning-distilled fine-tune of it, with about 3B active parameters. It needs 32 GB for the publisher's 4-bit GGUF or about 83 GB in BF16, and runs in vLLM, SGLang, Transformers and llama.cpp. The main risks are an undisclosed merge method, a card that disagrees with its files, and no safety results.

MiniMax-M3.1-Flash

A 428B mixture-of-experts model, 23B active, for agent work, coding and computer use, with image and video input, about 1M tokens of context and parallel tool calls. It needs a 4 to 8 GPU server for 250 GB of NVFP4 and MXFP8 weights, and vLLM and SGLang support was pre-release on 24 October 2026. Commercial use needs attribution and notice.

Darwin-36B-Opus

1. Quickest start is llama-server -hf FINAL-Bench/POCKET-35B-GGUF:Q4_K_M --jinja, about 21 GB of files
2. On the reference machine BF16 fits, vllm serve FINAL-Bench/Darwin-36B-Opus --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder, the parsers for Qwen3.6's format
3. Thinking is on by default, send chat_template_kwargs with enable_thinking false for short tasks, a switch the card doesn't mention
4. The card suggests temperature 0.6 to 0.7 and at least 5,120 new tokens for its think traces
5. generation_config.json stops only on the end-of-text token, so add <|im_end|> as a stop token if a runtime keeps generating after the turn ends
6. Text only, the vision encoder of Qwen3.6-35B-A3B isn't in these files
7. Validate JSON output yourself, since structured output isn't documented

MiniMax-M3.1-Flash

1. Check the use case first; commercial products must show "Built with MiniMax M3.1-Flash" and notify MiniMax once, or get written authorisation above $20M yearly revenue
2. On 8 H100 or H200 GPUs use vLLM's nightly image vllm/vllm-openai:minimax-m31-flash with --tensor-parallel-size 8 --block-size 128 --kv-cache-dtype fp8 --moe-backend marlin --max-model-len 262144
3. Pass --reasoning-parser minimax_m3 --tool-call-parser minimax_m3 --enable-auto-tool-choice in vLLM, or minimax-m3 for both in SGLang with --trust-remote-code
4. --block-size 128 is mandatory in vLLM, since MSA's sparse block size is 128
5. Set effort per request with chat_template_kwargs reasoning_effort (low, medium, high, xhigh, max); sample at temperature 1.0 and top_p 0.95
6. On Blackwell or MI355X, 4 GPUs serve it with the DSpark draft from dspark/; vLLM's Hopper command leaves DSpark off and turns video input off
7. For GGUF builds by others, use llama.cpp b11861 or later; earlier builds mis-scale the NVFP4 experts and produce garbage
8. Without the hardware, call MiniMax-M3.1-Flash on MiniMax's API (minimax-api), whose thinking defaults to max effort