LFM2.5-2.6B vs Nemotron 3.5 Lightning 30B A3B

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.

Nemotron 3.5 Lightning 30B A3B

A small agent cousin, 3B active parameters, with trained parallel tool calls, a thinking switch and up to 1M tokens of context, under a permissive licence. It runs in about 23 GB from the GGUF or Ollama builds, and NVIDIA's NVFP4 build needs NVIDIA GPUs. The main risks are no published safety results and one answered question across two repositories.

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

Nemotron 3.5 Lightning 30B A3B

1. Quickest start is ollama run nemotron-3.5-lightning, about 19 to 25 GB of files depending on the platform
2. On the reference machine use llama-server -hf ggml-org/NVIDIA-Nemotron-3.5-Lightning-30B-A3B-GGUF:Q4_0 --jinja, since the card's Q4_K_M tag doesn't exist there and NVFP4 needs NVIDIA GPUs
3. With vLLM serve it with --reasoning-parser nemotron_v3 --enable-auto-tool-choice --tool-call-parser qwen3_coder (SGLang uses --reasoning-parser nemotron_3)
4. Use temperature=1.0 and top_p=0.95, as the card says
5. Thinking is on by default. Pass chat_template_kwargs with enable_thinking false for short tasks
6. For coding agents pass force_nonempty_content: true in chat_template_kwargs, which vLLM's nemotron_v3 parser reads so a cut-off reasoning trace still returns content
7. Go past 262,144 tokens only with the card's flags (VLLM_ALLOW_LONG_MAX_MODEL_LEN=1, --max-model-len 1048576) and enough memory