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

LFM3-Omni-2B vs Qwen3.6-35B-A3B

Qwen3.6-35B-A3B scores 62.7 (B) on agent readiness against LFM3-Omni-2B's 61 (C), and leads in 2 of 4 scored categories. LFM3-Omni-2B leads on 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-Omni-2B C

Best for Voice and camera agents on a laptop or phone that want one small model for hearing, seeing, speaking and calling tools

Ahead on

  • Documentation and upkeep, 49 against 31

Watch for

Only llama.cpp and Ollama run it in a release

Qwen3.6-35B-A3B B

Best for Agents with a 32 GB or larger machine that want a quick, permissively licensed coding and tool-calling cousin with vision.

Ahead on

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

Watch for

No safety evaluation, no agent-use guidance and no way to report a security flaw

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-Omni-2B +18

LFM3-Omni-2B 49

Model card 14, Intended use (one on-device model in place of separate speech recognition, vision, language and speech models), architecture, parameters (2.17B), context (32K) and the text and speech languages. Training data 5, the card has no training section. Last change 20, the last commit, on 3 November 2026, changed the card's navigation icons, seven days before this check, and the one before it, on 28 October, documented video frame rate and frame limits. Responsiveness 0, none of the 12 discussions that aren't pull requests (27 October to 9 November 2026) has a reply from a LiquidAI member. Version policy 5, LFM3 came out in new repositories and the LFM2.5 models stay in theirs. File health 5, the card gives a 32K context while config.json gives the language model 128,000 positions and Liquid's API lists 128,000 for the hosted model, so the card and the files don't agree on context. 14 + 5 + 20 + 0 + 5 + 5 = 49.

Qwen3.6-35B-A3B 31

The model card earns 11, covering intended use, architecture, parameters and context but not limitations, languages or a cut-off. Training data earns 5 for a general description with no cut-off. The last change earns 5, a README edit on 24 April 2026, 192 days before this check, past 180 days and within a year, and Qwen's GitHub repository holds only a README and licence, so no reference code of Alibaba's changed later. Responsiveness earns 0, with no Qwen reply in the 40 most recent of 62 discussions that aren't pull requests, recounted on 2 November. Version policy earns 5, the earlier version kept in its own repository without a note. File health earns 5, the files agree but reports about tool calling and the template wait unanswered.

Risk Qwen3.6-35B-A3B +15

LFM3-Omni-2B 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-35B-A3B 55

File safety earns 25 for safetensors only, loaded by the runtimes' own code and a Jinja template with nothing run from the repository. Provenance earns 15, files in the Qwen organisation the publisher links and a hash for every file. Safety evaluation and agent guidance earn 0, since the card has neither safety results nor any guidance on refusals, injection or safeguards. Licence risk keeps all 15, as Apache 2.0 carries none of the four conditions and the late LICENSE file only wrote down what the card already said. The security programme earns 0, with no reporting route found on qwen.ai, the card or the GitHub repository, which is noted as unchecked for Alibaba's group-wide centre.

Reach Qwen3.6-35B-A3B +5

LFM3-Omni-2B 80

Memory 30, Liquid's Q4_K_M GGUF is 1.10 GB with its 0.29 GB projector file, and 1.39 GB × 1.2 = 1.7 GB, which fits 8 GB, well inside the 16 GB line. Runtimes 10, Released llama.cpp has the lfm3 architecture with the LFM3 vision and audio projectors and speech output (src/models/lfm3.cpp and tools/mtmd at b12242, with a realtime client example), and Ollama's library has an lfm3-omni entry. 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-omni-2b among its models, so the publisher hosts it. 30 + 10 + 15 + 10 + 10 + 5 = 80.

Qwen3.6-35B-A3B 85

Memory earns 20 because the smallest 4-bit build from a runtime's own library is Ollama's Q4_K_M at 23 GB, which comes to 27.6 GB with the fifth added, so it needs a 32 GB machine rather than a 24 GB one. Runtimes earn the full 25, since released llama.cpp, Ollama, vLLM, SGLang and Transformers all run the architecture. Builds earn 10 for Alibaba's one quantised build, FP8, with no 4-bit or GGUF from the publisher. Terms earn 15 for plain Apache 2.0, download earns 10 for ungated files, and hosted earns 5 because DeepInfra, Featherless AI and Scaleway serve it through Hugging Face.

Score by category

CategoryWeight this runLFM3-Omni-2BQwen3.6-35B-A3BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%258085Qwen3.6-35B-A3B +5
Risk20%204055Qwen3.6-35B-A3B +15
Agent interface10%107070even
Documentation and upkeep10%104931LFM3-Omni-2B +18
Negative events≤1500
TotalC 61/100B 62.7/100

Facts side by side

FactLFM3-Omni-2BQwen3.6-35B-A3B
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-032026-04-16
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviewsnone2.8/5 (4)

How the scores have moved

LFM3-Omni-2B

No score change since it was listed.

Qwen3.6-35B-A3B

Verdicts

LFM3-Omni-2B

One 2.17B model that sees, listens and talks on an 8 GB machine and turns spoken requests into tool calls. Only llama.cpp and Ollama run it in a release. The context is 32K, it doesn't reason, Liquid hasn't answered a question on the repository, and there are no safety results or data sources.

Qwen3.6-35B-A3B

A fast mixture-of-experts cousin with 3B active parameters for coding and tool calling, with image and video input, in every major runtime under plain Apache 2.0. Ollama's 4-bit build needs about 28 GB. The main risk is that nobody at Alibaba maintains it, with no safety results, no security contact and no replies to tool-calling reports.

Before you call either

LFM3-Omni-2B

  1. Start it with llama-server -hf LiquidAI/LFM3-Omni-2B-GGUF:Q4_K_M --jinja or ollama run lfm3-omni
  2. Greedy decoding for text. For speech use audio_temperature 0.4 and audio_repetition_penalty 1.2, per the card
  3. The context is 32K, and llama.cpp samples video at 2 frames a second up to 384 frames
  4. Parse tool calls yourself from the XML it returns
  5. It doesn't reason, so don't pass enable_thinking
  6. Validate JSON output yourself

Qwen3.6-35B-A3B

  1. Start it with ollama run qwen3.6:35b (Q4_K_M, 23 to 24 GB on disk, about 28 GB in memory)
  2. On the reference machine use vllm serve Qwen/Qwen3.6-35B-A3B --max-model-len 131072 --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder, BF16, since vLLM doesn't document FP8 compute on gfx1151
  3. Use the qwen3_coder tool-call parser and the qwen3 reasoning parser in vLLM 0.19.0 or SGLang 0.5.10 or later
  4. Thinking is on by default and /nothink isn't supported, so pass enable_thinking as false in chat_template_kwargs for short tasks, or preserve_thinking as true to keep earlier reasoning
  5. Card sampling for thinking is temperature 1.0, top_p 0.95, top_k 20, presence_penalty 1.5, and for non-thinking temperature 0.7, top_p 0.8
  6. Keep at least 128K of context as the card advises, and turn on YaRN only beyond 262,144 tokens
  7. Validate JSON output yourself or use the runtime's guided decoding, since the model card documents none

Questions

Which is better for AI agents, LFM3-Omni-2B or Qwen3.6-35B-A3B?

Qwen3.6-35B-A3B scores 62.7 (B) on agent readiness against LFM3-Omni-2B's 61 (C), and leads in 2 of 4 scored categories. LFM3-Omni-2B leads on documentation and upkeep.

Other comparisons with LFM3-Omni-2B or Qwen3.6-35B-A3B

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.