Laguna XS 2.1 vs Qwen3.5-9B

Laguna XS 2.1

A small coding and agent cousin with 3B active parameters, so it's quick on modest hardware. Poolside's 4-bit GGUF, also Ollama's default, needs about 24 GB, and every major runtime runs it. The main risks are that nobody at Poolside answers its discussions, there are no safety results, and the SGLang route runs repository code.

Qwen3.5-9B

A small dense vision-language cousin with trained tool calling, switchable thinking and a 262,144-token context, for local agent subtasks. Ollama's 4-bit build needs about 8 GB and the BF16 files about 24 GB, in every major runtime. The main risk is neglect, with no file changes since March, no replies from Qwen to reports and no safety results.

Laguna XS 2.1

1. Quickest start is ollama run laguna-xs-2.1, 20 GB of files, the same Q4_K_M as Poolside's GGUF
2. On our reference machine use llama-server -hf poolside/Laguna-XS-2.1-GGUF:Q4_K_M --jinja -c 131072, from a llama.cpp release with the laguna architecture (b11772 has it), or BF16 with vLLM (66.9 GB)
3. With vLLM use --tool-call-parser poolside_v1 --reasoning-parser poolside_v1 --enable-auto-tool-choice, on a build with vllm-project/vllm#47311, or --tool-call-parser glm47 on older builds
4. 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
5. Pass earlier reasoning back as reasoning_content in the history, since the card says reasoning may stop in later steps if it's dropped
6. Sampling per the card is temperature 1.0 and top_k 20
7. The card warns that Ollama on Apple Silicon may return empty output until llama.cpp#25389 ships
8. Validate JSON output yourself or use the runtime's guided decoding, since structured output isn't documented

Qwen3.5-9B

1. Smallest start is ollama run qwen3.5:9b (6.6 GB, q4_k_m)
2. On vLLM run vllm serve Qwen/Qwen3.5-9B --port 8000 --max-model-len 262144 --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder, or tool calls come back as text
3. Tool calls use the XML style <tool_call><function=name><parameter=x>, not Hermes JSON, so use the qwen3_coder parser and not hermes
4. Thinking is on by default; pass chat_template_kwargs with enable_thinking false for short tasks, since /nothink isn't supported
5. There's no generation_config.json, so pass sampling yourself, temperature 1.0, top_p 0.95, top_k 20, presence_penalty 1.5 when thinking, or 0.7, 0.8, 20, 1.5 without
6. Keep at least 128K of context when thinking, and turn on YaRN only beyond 262,144 tokens
7. Validate JSON output yourself or use the runtime's guided decoding