Laguna S 2.1 vs Qwen3-VL-32B-Instruct

Laguna S 2.1

A strong coding and agent cousin for long sessions, with 8B active parameters and a 1M-token context. At 4-bit it needs a 96 to 128 GB machine, tight on a 128 GB one. The main risks are that nobody at Poolside answers its many reports, there are no safety results, and a build card misdescribes its file.

Qwen3-VL-32B-Instruct

The largest dense Qwen3-VL cousin, for harder work on screenshots, documents, charts and video, needing about 25 GB from Alibaba's Q4_K_M GGUF with its vision file, in every major runtime under plain Apache 2.0. It has no thinking mode or published safety work, and only one provider was found serving it, so plan to run it yourself.

Laguna S 2.1

1. Quickest start is ollama run laguna-s-2.1, 96 GB for the default Q4_K_M, or the 66 GB nvfp4 tag on Apple Silicon
2. On our reference machine try llama-server -hf poolside/Laguna-S-2.1-GGUF:Q4_K_M --jinja -c 65536, from a llama.cpp release with the laguna architecture (b11772 has it). The 96 GB file leaves little room for context in 107.4 GB
3. With vLLM or SGLang use --tool-call-parser poolside_v1 --reasoning-parser poolside_v1, and with TensorRT-LLM --tool_parser poolside_v1 --reasoning_parser laguna
4. Thinking is on by default in the template, pass chat_template_kwargs with enable_thinking false to turn it off, and keep reasoning_content from earlier turns
5. The GGUFs ship set to 262,144 tokens. For 1M with llama.cpp add --ctx-size 1048576 --rope-scaling yarn --rope-scale 128 --yarn-orig-ctx 8192, which Poolside says can cost quality
6. Sampling per the generation config is temperature 1.0 and top_k 20, and Poolside suggests temperature 0.7 and top_p 0.95 at 1M
7. Expect occasional tool-schema slips in harnesses unlike Poolside's own, and validate JSON arguments, which Poolside lists as known limitations

Qwen3-VL-32B-Instruct

1. Start it with llama-server -hf Qwen/Qwen3-VL-32B-Instruct-GGUF:Q4_K_M --jinja -c 32768, or ollama run qwen3-vl:32b-instruct
2. In Ollama the plain qwen3-vl:32b tag is the Thinking edition, so name 32b-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 card's sampling, temperature=0.7, top_p=0.8, top_k=20, presence_penalty=1.5 for vision and temperature=1.0, top_p=1.0, top_k=40, presence_penalty=2.0 for text
6. Validate JSON output yourself, since structured output isn't documented
7. vLLM needs 0.11.0 or later and Transformers 4.57.0 or later
8. If you pulled the FP8 build before 22 October 2025, pull it again, since the earlier files were the Thinking edition's