Laguna M.1 vs MiniMax-M2.7

Laguna M.1

A large coding and agent cousin under plain Apache 2.0, for agents with a multi-GPU server. Its smallest build needs about 167 GB, more than a 128 GB machine, and no local runtime library packages it. The main risks are no upkeep since July, no hosted fallback shown today, no safety results, and repository code on the SGLang route.

MiniMax-M2.7

A 230B mixture-of-experts model for coding and agent harnesses, with parallel tool calls, about 200K of context and parsers in vLLM and SGLang. It needs a 4 GPU server for FP8 or about 166 GB for a 4-bit library build, and it always thinks. The main risk is the licence, switched to non-commercial two days after release.

Laguna M.1

1. Run the NVFP4 build on Blackwell GPUs with vllm serve poolside/Laguna-M.1-NVFP4 --tensor-parallel-size 2 --tool-call-parser poolside_v1 --reasoning-parser poolside_v1 --enable-auto-tool-choice, on vLLM 0.21.0 or later
2. Thinking is off in the template unless you pass enable_thinking true or start the server with --default-chat-template-kwargs '{"enable_thinking": true}', which Poolside recommends for agentic coding
3. Pass earlier reasoning back as reasoning_content in the history, since the card says reasoning may stop in later steps if it's dropped
4. Sampling per the card is temperature 1.0 and top_k 20
5. The FP8 build's Docker image and serve.sh predate upstream support and set a 4,096-token context, so prefer a released vLLM
6. It doesn't fit our 128 GB reference machine at any published precision
7. Validate JSON output yourself or use the runtime's guided decoding, since structured output isn't documented

MiniMax-M2.7

1. Check the use is personal, research or non-profit before starting it; anything commercial needs MiniMax's written authorisation, and commercial users must show Built with MiniMax M2.7
2. Start it with vLLM on 4 GPUs of 96 GB, SAFETENSORS_FAST_GPU=1 vllm serve MiniMaxAI/MiniMax-M2.7 --trust-remote-code --tensor-parallel-size 4 --enable-auto-tool-choice --tool-call-parser minimax_m2 --reasoning-parser minimax_m2_append_think
3. In SGLang use --tool-call-parser minimax-m2 and --reasoning-parser minimax-append-think, with --trust-remote-code
4. MiniMax's guides budget 220 GB for the weights and 240 GB per 1M tokens of KV cache, with 196K the most per sequence
5. On one large-memory machine, LM Studio's catalogue entry minimax/minimax-m2.7 lists a 138 GB Q4_K_M GGUF and states 138 GB minimum memory
6. Sample with temperature 1.0, top_p 0.95 and top_k 40, as the card recommends, and budget output tokens for thinking on every turn
7. Pin Transformers 4.57.1 as MiniMax's guide does; a report that it fails on Transformers v5 has no answer
8. Without the hardware, call it through Novita, Featherless AI or DeepInfra; MiniMax's own API retires M2.7 on 18 November 2026