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

LFM3-1.7B vs Qwen3.6-27B

Qwen3.6-27B scores 66.7 (B) on agent readiness against LFM3-1.7B's 61 (C), and leads in 2 of 4 scored categories. LFM3-1.7B leads on agent interface and documentation and upkeep. 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 31

Watch for

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

Qwen3.6-27B B

Best for Agents that want an open coding and tool-calling model with vision on one 24 to 32 GB GPU or Mac, with plain licence terms.

Ahead on

  • Reach, 90 against 85
  • Risk, 55 against 40

Watch for

No safety results, prompt-injection guidance or security contact

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 +36

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.6-27B 31

Model card 11 of 20, intended use, architecture, parameters and context are there, but limitations, languages and a knowledge cut-off aren't. Training data 5, only a general family description without a cut-off, in the GitHub README. Last change 5, the files last changed on 24 April 2026, 191 days before this check, and Qwen's GitHub repository holds only a README and licence, so no reference code of Alibaba's changed later. Responsiveness 0, Qwen answered none of the 40 most recent questions and reports, recounted on 1 November. Version policy 5, earlier and later 27B models stay in their own repositories without dated notes. File health 5, the files agree with the card but template and tool-calling reports wait without a reply.

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.6-27B 70

Chat template 20, a Jinja file in the repository. Tool-calling format 10 of 25, the card names the qwen3_coder parser but the declaration and call format live only in the template. Trained tool calling 20, the template renders several calls in one turn. Structured output 0, not documented. Reasoning control 10, thinking turns off per request and comes back in think tags split out by the qwen3 parser. Context 10, 262,144 tokens native.

Risk Qwen3.6-27B +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.6-27B 55

File safety 25, safetensors only and nothing from the repository runs to load it or build prompts. Provenance 15, the files are in the Qwen organisation that Qwen's GitHub links to, and every file has a hash on the Hub. Safety evaluation 0, none published on the card or README. Agent guidance 0, nothing on prompt injection, refusals or safeguards. Licence risk 15, plain Apache 2.0 that hasn't changed. Security programme 0, no security.txt, SECURITY.md or reporting route was found, and Alibaba's group security centre couldn't be checked, so it's scored as absent.

Reach Qwen3.6-27B +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.6-27B 90

Memory 25 of 30, Ollama's text-only 4-bit build is 17 GB and the vision build 18 GB, about 20 to 22 GB with a fifth added, which fits 24 GB. Runtimes 25, released versions of llama.cpp, Ollama, vLLM, SGLang, LM Studio and Transformers all run the qwen3_5 architecture. Builds 10 of 15, Alibaba's only quantised build is FP8. Terms 15, Apache 2.0 with nothing added. Download 10, neither repository is gated. Hosted 5, three inference providers are live on Hugging Face and Alibaba's Model Studio serves it per the card.

Score by category

CategoryWeight this runLFM3-1.7BQwen3.6-27BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%258590Qwen3.6-27B +5
Risk20%204055Qwen3.6-27B +15
Agent interface10%1010070LFM3-1.7B +30
Documentation and upkeep10%106731LFM3-1.7B +36
Negative events≤1500
TotalC 61/100B 66.7/100

Facts side by side

FactLFM3-1.7BQwen3.6-27B
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-04-22
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviewsnone3/5 (4)

How the scores have moved

LFM3-1.7B

No score change since it was listed.

Qwen3.6-27B

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.6-27B

A capable dense cousin for agentic coding and tool calls with images and video in, running in every major runtime. Ollama's 4-bit build needs about 22 GB, and three providers host it. The main risk is silence, with no safety results, no agent guidance, no answers in its repository and Qwen3.8-27B now ahead of it.

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.6-27B

  1. Quickest start is ollama run qwen3.6:27b, about 18 GB of files with the vision projector
  2. Alibaba's FP8 build with the card's parsers is vllm serve Qwen/Qwen3.6-27B-FP8 --max-model-len 262144 --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder, vllm 0.19.0 or later
  3. Use the qwen3_coder tool parser, the template writes calls as function and parameter blocks inside tool_call
  4. Thinking is on by default, pass "chat_template_kwargs": {"enable_thinking": false} for short tasks, and /think and /nothink aren't supported
  5. "preserve_thinking": true in chat_template_kwargs keeps earlier reasoning in context, which helps long agent sessions but grows the prompt
  6. Sampling per the card is temperature 1.0, top_p 0.95, top_k 20 when thinking, and temperature 0.7, top_p 0.8, presence_penalty 1.5 without
  7. Keep at least 128K of context if you rely on thinking, and turn on YaRN only beyond 262,144 tokens
  8. Validate any JSON it returns or use the runtime's guided decoding, since structured output isn't documented
  9. Qwen3.8-27B (listed as qwen3-8-27b) is the newer model at this size on the same runtimes

Questions

Which is better for AI agents, LFM3-1.7B or Qwen3.6-27B?

Qwen3.6-27B scores 66.7 (B) on agent readiness against LFM3-1.7B's 61 (C), and leads in 2 of 4 scored categories. LFM3-1.7B leads on agent interface and documentation and upkeep.

Other comparisons with LFM3-1.7B or Qwen3.6-27B

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.