Laguna S 2.1 vs Qwen3-Coder-30B-A3B-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-Coder-30B-A3B-Instruct

A fast coding cousin, with 3.3B of 30.5B parameters active per token, for agentic coding tools, repository reading and fill-in-the-middle without a thinking step. It needs about 21 to 23 GB at 4 bits, and several providers host it. The main risk is that it runs commands for agents with no safety results or guidance, and Alibaba doesn't answer users.

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

1. Quickest start is ollama run qwen3-coder:30b, 19 GB
2. On our reference machine use BF16 with vllm serve Qwen/Qwen3-Coder-30B-A3B-Instruct --max-model-len 262144 --enable-auto-tool-choice --tool-call-parser qwen3_coder, 61 GB of weights fits the GPU share
3. Use the qwen3_coder parser in vLLM or SGLang, not hermes, since calls come back as function and parameter blocks rather than JSON
4. Pass tool-call arguments in the history as objects, the template iterates them as a mapping
5. Sampling per the card is temperature 0.7, top_p 0.8, top_k 20 and repetition_penalty 1.05, with up to 65,536 output tokens
6. For code completion use the fill-in-the-middle tokens <|fim_prefix|>, <|fim_suffix|> and <|fim_middle|> from Qwen's README
7. Sandbox the commands and files it touches, since nothing from Alibaba covers prompt injection