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

LFM3-Omni-2B vs Qwen3.5-397B-A17B

Qwen3.5-397B-A17B scores 64.1 (B) on agent readiness against LFM3-Omni-2B's 61 (C), and leads in 1 of 4 scored categories. LFM3-Omni-2B leads on reach 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-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

  • Reach, 80 against 70
  • Documentation and upkeep, 49 against 34

Watch for

Only llama.cpp and Ollama run it in a release

Qwen3.5-397B-A17B B

Best for Agents with access to an 8-GPU server, or calling a hosted endpoint, that want the strongest open Qwen3.5 with vision and a plain licence.

Ahead on

  • Risk, 55 against 40

Watch for

No build fits a 256 GB machine, and Ollama has no local build

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.

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

Safetensors only with no repository code run on load or to build prompts gives file safety 25, and files in the Qwen organisation the publisher's GitHub links to, each hashed on the Hub, give provenance 15. Plain Apache 2.0 keeps licence risk at 15. Safety evaluation, agent guidance and a security programme score 0. The card has no safety results (its SecCodeBench row is a coding capability), no cautions, and no reporting route was found. The Qwen3.5 blog and Alibaba's security response centre couldn't be read, so both are scored as absent and left open.

Documentation and upkeep LFM3-Omni-2B +15

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.5-397B-A17B 34

The card covers five of the seven items and misses limitations and a cut-off (14). Training data is a general description without a cut-off (5). The files last changed on 24 April 2026, 192 days before this check, past the 180-day band and within a year (5), and Qwen's GitHub repository holds only a README and licence, so no reference code of Alibaba's changed later. Alibaba answered none of the 40 most recent questions and reports, recounted on 2 November (0), and GitHub issues couldn't be counted. It's a first release at this size (5), and two template reports and a template fix still wait unanswered (5). 14 + 5 + 5 + 0 + 5 + 5 = 34.

Reach LFM3-Omni-2B +10

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.5-397B-A17B 70

Memory scores 0, since even the smallest 4-bit build, LM Studio's MLX 4-bit at 223.9 GB, needs about 269 GB with a fifth added, and Alibaba's own GPTQ-Int4 about 283 GB. Runtimes reach the 25 cap on released llama.cpp, vLLM, SGLang and Transformers and LM Studio's catalogue, though Ollama has no local build. Alibaba's FP8 and GPTQ-Int4 builds give builds 15. Apache 2.0 with nothing added gives terms 15, the ungated repositories give download 10, and Alibaba's Model Studio plus five live providers on Hugging Face give hosted too its 5.

Score by category

CategoryWeight this runLFM3-Omni-2BQwen3.5-397B-A17BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%258070LFM3-Omni-2B +10
Risk20%204055Qwen3.5-397B-A17B +15
Agent interface10%107070even
Documentation and upkeep10%104934LFM3-Omni-2B +15
Negative events≤1500
TotalC 61/100B 64.1/100

Facts side by side

FactLFM3-Omni-2BQwen3.5-397B-A17B
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-02-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

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.5-397B-A17B

Alibaba's biggest open Qwen3.5, a cousin for hard coding, agent and vision work. Even at 4 bits it needs about 270 GB, so most agents will call it through Alibaba's Model Studio or one of the many providers that host it. The main risk is silence, with no safety results, no agent guidance and template reports without a reply.

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.5-397B-A17B

  1. The card's server command is vllm serve Qwen/Qwen3.5-397B-A17B --port 8000 --tensor-parallel-size 8 --max-model-len 262144 --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder, and the FP8 build halves the memory
  2. It doesn't fit our 128 GB reference machine at any precision, so call a hosted endpoint instead (Model Studio's Qwen3.5-Plus, or a provider serving Qwen/Qwen3.5-397B-A17B)
  3. On Model Studio pass "enable_thinking": false directly, while vLLM and SGLang take "chat_template_kwargs": {"enable_thinking": false}
  4. Sampling per the card is temperature 0.6, top_p 0.95 and top_k 20 when thinking, and temperature 0.7, top_p 0.8, top_k 20 and presence_penalty 1.5 without
  5. For multi-token prediction in vLLM add --speculative-config '{"method":"qwen3_next_mtp","num_speculative_tokens":2}'
  6. Keep the context at 128K or more if you rely on thinking, and turn on YaRN only past 262,144 tokens
  7. Validate any JSON it returns, since structured output isn't documented

Questions

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

Qwen3.5-397B-A17B scores 64.1 (B) on agent readiness against LFM3-Omni-2B's 61 (C), and leads in 1 of 4 scored categories. LFM3-Omni-2B leads on reach and documentation and upkeep.

Other comparisons with LFM3-Omni-2B or Qwen3.5-397B-A17B

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.