GLM-4.7-Flash vs MiniMax-M3.1-Flash

GLM-4.7-Flash

A small MIT-licensed mixture-of-experts model with about 3B active parameters, for local agent and coding work with several tool calls per turn and optional thinking. It runs in Ollama at about 23 GB and in nearly every common runtime. The main risk is neglect, with no changes or replies since early February 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.

GLM-4.7-Flash

1. On our reference machine start it with vllm serve zai-org/GLM-4.7-Flash --max-model-len 65536 --tool-call-parser glm47 --reasoning-parser glm45 --enable-auto-tool-choice --served-model-name glm-4.7-flash
2. Or run ollama run glm-4.7-flash for the 19 GB q4_K_M build
3. Without the glm47 and glm45 parsers, tool calls and reasoning come back as plain text
4. Use a released vLLM (0.32.0 or later) or SGLang (0.5.22 or later); the card's nightly and pull-request builds date from January 2026
5. Pass chat_template_kwargs: {"enable_thinking": false} for short tasks, since thinking is on by default
6. Set clear_thinking: false to keep earlier reasoning in multi-turn agent work, as Z.ai does for τ²-Bench and Terminal Bench
7. Set the context length yourself, since config.json allows 202,752 tokens and tokenizer_config.json says 128,000

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