LFM2.5-2.6B vs Qwen3.5-397B-A17B

LFM2.5-2.6B

A small, fast cousin for tool calls, extraction and long-context steps on a laptop or phone. Liquid's own 4-bit build is 1.6 GB, and every common runtime runs it. It always thinks, isn't meant for coding or knowledge-heavy work, and organisations over $10M of revenue need another licence. There are no safety results or security contact.

Qwen3.5-397B-A17B

Alibaba's biggest open Qwen3.5, a cousin for hard coding, agent and vision work. Even at 4 bits it needs about 270 GB, so most agents will call it through Alibaba's Model Studio or one of the many providers that host it. The main risk is silence, with no safety results, no agent guidance and template reports without a reply.

LFM2.5-2.6B

1. Quickest start is ollama run LiquidAI/lfm2.5-2.6b, 1.7 GB, or llama-cli -hf LiquidAI/LFM2.5-2.6B-GGUF
2. With vLLM or SGLang pass --tool-call-parser lfm2; for vLLM add --reasoning-parser qwen3 so the thinking comes back separately
3. Sample at temperature 0.1, top_k 50 and repetition_penalty 1.1, as the card and generation_config.json set
4. Put tools in the system prompt as List of tools: [...] JSON, or pass tools to apply_chat_template; calls come back as a Python list of function calls, and the system prompt can ask for JSON calls instead
5. Leave max_tokens unset or generous, since a low cap cuts the reasoning off mid-thought
6. Earlier thinking is dropped from the prompt unless preserve_thinking is true
7. Liquid's 328M LFM2.5-2.6B-DSpark drafter speeds decoding about 2.6 times in SGLang and on Apple silicon, per Liquid
8. Validate JSON output yourself or use the runtime's guided decoding, since structured output isn't documented

Qwen3.5-397B-A17B

1. The card's server command is vllm serve Qwen/Qwen3.5-397B-A17B --port 8000 --tensor-parallel-size 8 --max-model-len 262144 --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder, and the FP8 build halves the memory
2. It doesn't fit our 128 GB reference machine at any precision, so call a hosted endpoint instead (Model Studio's Qwen3.5-Plus, or a provider serving Qwen/Qwen3.5-397B-A17B)
3. On Model Studio pass "enable_thinking": false directly, while vLLM and SGLang take "chat_template_kwargs": {"enable_thinking": false}
4. Sampling per the card is temperature 0.6, top_p 0.95 and top_k 20 when thinking, and temperature 0.7, top_p 0.8, top_k 20 and presence_penalty 1.5 without
5. For multi-token prediction in vLLM add --speculative-config '{"method":"qwen3_next_mtp","num_speculative_tokens":2}'
6. Keep the context at 128K or more if you rely on thinking, and turn on YaRN only past 262,144 tokens
7. Validate any JSON it returns, since structured output isn't documented