DeepSeek-V3.2 vs Laguna M.1

DeepSeek-V3.2

DeepSeek-V3.2 is an MIT-licensed reasoning model trained for parallel tool calls, with thinking chosen per request, for long agent work. It needs about 690 GB of FP8 files, eight 80 GB GPUs in vLLM's recipe and prompts built from DeepSeek's Python. The main risk is neglect, with no file changes since December 2025 and no safety evaluation.

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.

DeepSeek-V3.2

1. Start it with vLLM's recipe, vllm serve deepseek-ai/DeepSeek-V3.2 --tensor-parallel-size 8 --tokenizer-mode deepseek_v32 --enable-auto-tool-choice --tool-call-parser deepseek_v32 --reasoning-parser deepseek_v3
2. It doesn't fit the 107.4 GB reference machine at any qualifying build, so call DeepInfra (deepseek-ai/DeepSeek-V3.2) or SambaNova (DeepSeek-V3.2) instead
3. Outside vLLM, build prompts with encoding/encoding_dsv32.py and wrap parse_message_from_completion_text in error handling, since DeepSeek says it handles well-formed output only
4. Pick thinking or chat with thinking_mode, and read the reasoning from reasoning_content
5. Send developer messages only for search-agent prompts, the only use DeepSeek gives that role
6. Use temperature 1.0 and top_p 0.95 and keep prompts within 128K tokens

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