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

LFM3-1.7B vs Qwen3.5-2B

LFM3-1.7B scores 61 (C) on agent readiness against Qwen3.5-2B's 50.5 (D), and leads in 3 of 4 scored categories. Qwen3.5-2B 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

  • Reach, 85 against 80
  • Agent interface, 100 against 60
  • Documentation and upkeep, 67 against 37

Watch for

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

Qwen3.5-2B D

Best for Builders who want a cheap local helper or fine-tuning base for narrow tasks and image reading on a laptop, small GPU or CPU

Ahead on

  • Risk, 55 against 40

Watch for

No quantised build from Alibaba, and only one inference provider

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.

Agent interface LFM3-1.7B +40

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-2B 60

The template ships in the repository (20) and the model was trained for tool use with several calls per turn in the template (20). Tool-calling format gets 10, because the card names the qwen3_coder parser but leaves the format to the template. Reasoning control scores 0, since the card shows how to turn thinking on but not where the reasoning comes back. 262,144 tokens is native (10). Structured output scores 0, as nothing documents JSON output for the model. 20+10+20+0+0+10 = 60.

Documentation and upkeep LFM3-1.7B +30

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-2B 37

The card covers six of the seven items, missing only a cut-off (17), because it states the intended uses and warns about thinking loops. Training data is a general description without a cut-off (5). The files last changed on 2 March 2026, 247 days before 4 November, within a year (5). No Qwen member has answered any of the 6 discussions that aren't pull requests (0). Qwen3-1.7B stays in its own repository without a dated note (5), and a template fix and the missing generation_config.json wait unanswered (5). 17+5+5+0+5+5 = 37.

Risk Qwen3.5-2B +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-2B 55

Safetensors only with no remote code gives file safety its 25, and files in the Qwen organisation the publisher's GitHub links to, each with a hash on the Hub, give provenance 15. The Apache 2.0 licence carries none of the deductions, so licence risk keeps 15. Safety evaluation, agent guidance and a security programme score 0, since the card has no safety results or agent cautions and no reporting route was found. The Qwen3.5 blog and Alibaba's security response centre couldn't be read, so those are scored as absent and left open. 25+15+0+0+15+0 = 55.

Reach LFM3-1.7B +5

LFM3-1.7B 85

Memory 30, Liquid's Q4_K_M GGUF is 1.10 GB, and 1.10 GB × 1.2 = 1.3 GB, which fits 8 GB, well inside the 16 GB line. Runtimes 15, Released llama.cpp has the lfm3 architecture (src/models/lfm3.cpp at b12242), Ollama's library has an lfm3 entry, and LM Studio's catalogue runs the architecture (its liquid/lfm3-vl-2b entry; lmstudio-community publishes a GGUF of this model). Builds 15, Liquid's GGUF repository holds Q4_0, Q4_K_M, Q8_0, F16 and BF16 files, and Liquid publishes 4-bit and 8-bit MLX builds and an ONNX repository, all in the LiquidAI organisation. Terms 10, the LFM Open License v1.0, a custom licence that lets anyone use it commercially for free below a threshold of $10M annual revenue. Download 10, the Hub API reports gated false for the model and its GGUF, MLX and ONNX repositories on 10 November 2026, so the files download with no account and nothing to accept. Hosted 5, Liquid's own API lists lfm3-1.7b among its models, so the publisher hosts it. 30 + 15 + 15 + 10 + 10 + 5 = 85.

Qwen3.5-2B 80

Memory earns the full 30, since LM Studio's Q4_K_M GGUF with its vision projector is 1.94 GB, about 2.3 GB with the fifth added (Ollama's Q4_K_M build was 1.9 GB on 21 October). Alibaba publishes no quantised 2B, so builds scores 0. Runtimes reach the 25 cap, with llama.cpp b11963 and Ollama through the build it pins re-read today. Apache 2.0 with nothing added gives terms 15 and the ungated download 10. Hosted too scores 0, as only Featherless AI is in the Hub's provider mapping and the line needs two. 30+25+0+15+10+0 = 80.

Score by category

CategoryWeight this runLFM3-1.7BQwen3.5-2BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%258580LFM3-1.7B +5
Risk20%204055Qwen3.5-2B +15
Agent interface10%1010060LFM3-1.7B +40
Documentation and upkeep10%106737LFM3-1.7B +30
Negative events≤1500
TotalC 61/100D 50.5/100

Facts side by side

FactLFM3-1.7BQwen3.5-2B
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 reviewsnone3/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-2B

A small vision-language model for prototypes, fine-tuning and narrow local steps such as tool calls, tagging or reading an image. It runs in about 2 GB at 4 bits in six runtimes under plain Apache 2.0. Keep thinking off, since the card warns it loops. The card has no safety results, and Qwen has answered none of its discussions.

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-2B

  1. Smallest start is ollama run qwen3.5:2b-q4_K_M (1.9 GB); plain qwen3.5:2b pulls the 2.7 GB Q8_0 build
  2. Full precision vllm serve Qwen/Qwen3.5-2B --port 8000 --max-model-len 262144 --enable-auto-tool-choice --tool-call-parser qwen3_coder
  3. Thinking is off by default; if you turn it on with "chat_template_kwargs": {"enable_thinking": true}, stream and cut off runaway output, since the card warns of thinking loops, and add --reasoning-parser qwen3 in vLLM or SGLang to split the reasoning out
  4. There's no generation_config.json, so pass the card's sampling yourself, for example temperature=1.0, top_p=1.0, top_k=20, presence_penalty=2.0 for text without thinking
  5. Use it for narrow steps or as a fine-tuning base, not as the main agent, as the card itself suggests
  6. Validate any JSON it returns, since structured output isn't documented

Questions

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

LFM3-1.7B scores 61 (C) on agent readiness against Qwen3.5-2B's 50.5 (D), and leads in 3 of 4 scored categories. Qwen3.5-2B leads on risk.

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

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.