Laguna M.1 vs Qwen3.5-2B

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.

Qwen3.5-2B

A small vision-language cousin for prototypes, fine-tuning and light local steps such as tool calls, tagging or reading an image, running in about 2 GB at 4 bits in every major runtime under plain Apache 2.0. Keep thinking off, since the card warns it loops. The main risk is neglect, with no safety results or answers from Alibaba since March.

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

Qwen3.5-2B

1. Smallest start is ollama run qwen3.5:2b-q4_K_M (1.9 GB); plain qwen3.5:2b pulls the 2.7 GB Q8_0 build
2. Full precision vllm serve Qwen/Qwen3.5-2B --port 8000 --max-model-len 262144 --enable-auto-tool-choice --tool-call-parser qwen3_coder
3. Thinking is off by default; if you turn it on with "chat_template_kwargs": {"enable_thinking": true}, stream and cut off runaway output, since the card warns of thinking loops, and add --reasoning-parser qwen3 in vLLM or SGLang to split the reasoning out
4. There's no generation_config.json, so pass the card's sampling yourself, for example temperature=1.0, top_p=1.0, top_k=20, presence_penalty=2.0 for text without thinking
5. Use it for narrow steps or as a fine-tuning base, not as the main agent, as the card itself suggests
6. Validate any JSON it returns, since structured output isn't documented