Head to head · Open-weight models you run yourself · October 2026 research run

LFM3-1.7B vs Qwen3.5-9B

LFM3-1.7B and Qwen3.5-9B score within a point of each other on agent readiness, 61 (C) and 60.5 (C). Qwen3.5-9B leads on risk. Both do open-weight models you run yourself.

Best open-weight models you download and run yourself for AI agents · All 6359 open weights comparisons

Which one, for what

LFM3-1.7B C

Best for Agents on a laptop, phone or small server that need tool calling and a long context from a model under 2 GB at 4 bits

Ahead on

  • Agent interface, 100 against 70
  • Documentation and upkeep, 67 against 34

Watch for

vLLM and SGLang have no released support, though the card lists both

Qwen3.5-9B C

Best for Agents that want a small multimodal tool-calling model on a laptop or a 16 GB GPU, under a plain licence

Ahead on

  • Risk, 55 against 40

Watch for

No quantised build from Qwen itself

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Documentation and upkeep LFM3-1.7B +33

LFM3-1.7B 67

Model card 17, Intended use (local agents, tool calling, structured outputs, fine-tuning), a limitation (not recommended for agentic coding or complex multi-step reasoning), architecture (24 layers: 13 gated short convolutions, 5 sliding-window and 6 global attention), parameters (1.73B), context (256K) and 16 languages. Training data 5, A general description: 22T tokens of pre-training in two stages with the kinds of data added since LFM2, 1.75T tokens of supervised fine-tuning, then mixed reinforcement learning, distillation from six specialist teachers and agentic reinforcement learning. Last change 20, the last commit, on 9 November 2026, added the OpenVINO checkpoint to the card's inference table, a day before this check. Responsiveness 10, Of the 22 discussions that aren't pull requests (27 October to 8 November 2026), 7 have a reply from a LiquidAI member, which is some. Version policy 5, LFM3 came out in new repositories and the LFM2.5 models stay in theirs. File health 10, Config, template and card agree on the lfm3 architecture, the 262,144-token context and the thinking switch. 17 + 5 + 20 + 10 + 5 + 10 = 67.

Qwen3.5-9B 34

Model card 14, it covers intended use, architecture, parameters, context and 201 languages but gives no limitations and no knowledge cut-off. Training data 5, a general line about trillions of multimodal tokens with no cut-off. Last change 5, the files and card last changed on 2 March 2026 (c202236), 247 days before 4 November, within a year. Responsiveness 0, no Qwen member replied in any of the 40 most recent of the 45 discussions that aren't pull requests (2 March to 29 September 2026). Version policy 5, a first release that was never replaced in place, with no dated notes across generations. File health 5, two reports about the files and card (15 and 51) are still open with no reply. 14 + 5 + 5 + 0 + 5 + 5 = 34. The card's highlights mention sparse Mixture-of-Experts for the series while this 9B is dense, but its own overview matches config.json, so it's not counted as a contradiction.

Agent interface LFM3-1.7B +30

LFM3-1.7B 100

Chat template 20, chat_template.jinja in the repository (12,129 characters), with roles, tools, deferred tools, tool results and the thinking switch. Tool-calling format 25, the card and Liquid's tool-use page document tools passed through tools= in apply_chat_template, calls returned as XML and results sent back as tool messages. Trained tool calling 20, the template loops over every entry in an assistant turn's tool_calls, so several calls fit in one turn, and the card says the model was trained on tool calls and agentic traces and with reinforcement learning inside agent harnesses. Structured output 15, Liquid's API guide documents response_format with a JSON Schema, with lfm3-1.7b as the model in its examples, and says the schema is checked before generation starts. Reasoning control 10, the card documents enable_thinking=False in the chat template to turn reasoning off per request, with reasoning on by default inside think tags, and preserve_thinking for earlier turns. Context 10, 256K tokens per the card, which says the mid-training stage extended the context window to 256K, and max_position_embeddings 262144 in config.json. 20 + 25 + 20 + 15 + 10 + 10 = 100.

Qwen3.5-9B 70

Chat template 20, a Jinja file in the repository. Tool-calling format 10, the card names the qwen3_coder parser for vLLM and SGLang but leaves the declaration and return format to the template, and Qwen's own function-calling guide still describes Qwen3's Hermes format. Trained tool calling 20, the template renders several calls in one turn. Structured output 0, nothing documents asking the weights for JSON. Reasoning control 10, thinking turns off per request with enable_thinking false and the reasoning comes back in think tags that the qwen3 parser splits out. Context 10, 262,144 tokens native.

Risk Qwen3.5-9B +15

LFM3-1.7B 40

File safety 15, safetensors only, no .bin, .pt or .pth files (25). Provenance 15, files in the LiquidAI organisation, which Liquid's docs page for the model and its blog post link to (10). Safety evaluation 0, no safety results on the card or in Liquid's blog post for the LFM3 family, neither of which mentions safety testing. Agent guidance 0, Nothing on prompt injection, an instruction hierarchy, what refusals cover or safeguards to add. Licence risk 10, 15 less 5 for the $10M annual revenue threshold on commercial use. Security programme 0, no way to report a flaw found. 15 + 15 + 0 + 0 + 10 + 0 = 40.

Qwen3.5-9B 55

File safety 25, safetensors only and nothing from the repository runs on load or to build prompts. Provenance 15, the Qwen organisation linked from Alibaba's QwenLM README, with a SHA-256 for every shard. Safety evaluation 0, none on the card, and the Qwen3.5 blog couldn't be read, so this is couldn't check scored as absent. Agent guidance 0, the card has no prompt-injection guidance, refusal scope or cautions. Licence risk 15, Apache 2.0 with nothing added and a working licence link. Security programme 0, no SECURITY.md in Qwen's GitHub repositories, no security.txt on qwen.ai or alibabacloud.com, and whether Alibaba's group security centre takes reports about Qwen models couldn't be checked.

Score by category

CategoryWeight this runLFM3-1.7BQwen3.5-9BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%258585even
Risk20%204055Qwen3.5-9B +15
Agent interface10%1010070LFM3-1.7B +30
Documentation and upkeep10%106734LFM3-1.7B +33
Negative events≤1500
TotalC 61/100C 60.5/100

Facts side by side

FactLFM3-1.7BQwen3.5-9B
KindOpen-weight modelOpen-weight model
VendorLiquid AIAlibaba (Qwen team)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceLFM Open License v1.0 (free commercial use below $10M annual revenue)Apache-2.0
Read-only variant documentednono
llms.txtyesno
Last release2026-11-092026-03-02
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviewsnone2.5/5 (4)

Verdicts

LFM3-1.7B

A 1.73B model that fits an 8 GB machine with room to spare, with a documented tool-call format, deferred tools, a thinking switch and a 256K context. It runs today in llama.cpp, Ollama and LM Studio only, loads in Transformers through repository code, and has no safety results, security contact or data sources.

Qwen3.5-9B

A small dense vision-language model with trained tool calling, thinking that turns off per request and a 262,144-token context. Ollama's 4-bit build is 6.6 GB and the BF16 files 19.3 GB, and every major runtime loads it. The files haven't changed since 2 March 2026, Qwen answered none of the 40 latest discussions, and no safety results are published.

Before you call either

LFM3-1.7B

  1. Start it with llama-server -hf LiquidAI/LFM3-1.7B-GGUF:Q4_K_M --jinja or ollama run lfm3
  2. Use temperature 0.1, top_k 50 and repetition penalty 1.1 for chat, tools and agents, per the card
  3. Pass enable_thinking=False for direct answers, and expect it to reason anyway on hard tasks
  4. For a large tool catalogue mark tools defer_loading and give it a search tool
  5. Don't plan on vLLM or SGLang until a release carries LFM3
  6. Liquid doesn't recommend it for agentic coding or complex multi-step reasoning

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

Questions

Which is better for AI agents, LFM3-1.7B or Qwen3.5-9B?

LFM3-1.7B and Qwen3.5-9B score within a point of each other on agent readiness, 61 (C) and 60.5 (C). Qwen3.5-9B leads on risk.

Other comparisons with LFM3-1.7B or Qwen3.5-9B

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.