Laguna M.1 vs Qwen3-VL-30B-A3B-Instruct

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-VL-30B-A3B-Instruct

A mid-sized vision-language cousin for screenshots, documents, charts and video that runs fast for its size, with about 3B active parameters. It needs about 23 GB for Alibaba's Q4_K_M GGUF with its vision file, loads in every major runtime under plain Apache 2.0, and three providers host it. With no published safety work, add guardrails before it drives a GUI.

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-VL-30B-A3B-Instruct

1. Start it with llama-server -hf Qwen/Qwen3-VL-30B-A3B-Instruct-GGUF:Q4_K_M --jinja -c 32768, or ollama run qwen3-vl:30b-a3b-instruct
2. In Ollama the plain qwen3-vl:30b tag is the Thinking edition, so name 30b-a3b-instruct
3. With the GGUF, load the mmproj vision file too, or images won't be read
4. Parse tool calls as JSON inside <tool_call> tags, or use SGLang's --tool-call-parser qwen
5. Use the shipped sampling, temperature 0.7, top_p 0.8 and top_k 20, from generation_config.json
6. Validate JSON output yourself, since structured output isn't documented
7. vLLM needs 0.11.0 or later, Transformers 4.57.0 or later and llama.cpp b6907 or later