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

LBS-27B vs LFM3-Omni-2B

LFM3-Omni-2B scores 61 (C) on agent readiness against LBS-27B's 55.8 (C), and leads in 2 of 4 scored categories. LBS-27B leads on risk. Both do open-weight models you run yourself.

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

Which one, for what

LBS-27B C

Best for Agents with about 96 GB of GPU memory that need to find click targets on dense professional screenshots, or read fine detail in large images, and can run a small crop loop and wait for independent results.

Ahead on

  • Risk, 50 against 40

Watch for

No independent benchmark result yet; ScreenSpot-Pro, OS-World-G, PerceptionBench and HR-Bench numbers are inclusionAI's own runs

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 60
  • Documentation and upkeep, 49 against 43

Watch for

Only llama.cpp and Ollama run it in a release

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.

Reach LFM3-Omni-2B +20

LBS-27B 60

Memory earns 10, since the only build is 54.73 GB of BF16, about 66 GB with a fifth added, which fits the reference machine but not 64 GB. Runtimes earn 25 from released vLLM, SGLang, Transformers and llama.cpp, which all carry Qwen3.8-27B's architecture, and Ollama through the llama.cpp release it pins, so 25. Builds earn 0, as inclusionAI publishes no quantised build and the GGUF copies are bartowski's and mradermacher's. Terms earn 15 for Apache 2.0 with nothing added, on the weights and on the base. Download earns 10, with no gate. Hosted earns 0, as no provider or inclusionAI API serves it.

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.

Risk LBS-27B +10

LBS-27B 50

File safety earns 15, safetensors only but with the documented route running the publisher's scripts to serve it and to write its system prompt. Provenance earns 15, inclusionAI's own organisation with a hash for every file. Safety evaluation and agent guidance earn 0, as nothing is published on either, prompt injection through screenshots included. Licence risk keeps all 15 under Apache 2.0. The security programme earns 5 for Ant Group's AntSRC, which isn't linked to the model.

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.

Documentation and upkeep LFM3-Omni-2B +6

LBS-27B 43

The model card earns 8, with intended use, one limitation and parameters, and no architecture, context, languages or cut-off. Training data earns 5 for a general description of synthetic GUI data with no cut-off. Last change earns 20 for 26 October 2026. Responsiveness earns 0, the one discussion unanswered. Version policy earns 5 for a first release. File health earns 5, as the config still sets an MTP layer the weights lack and the card names a reasoning setting the template refuses.

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.

Score by category

CategoryWeight this runLBS-27BLFM3-Omni-2BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%256080LFM3-Omni-2B +20
Risk20%205040LBS-27B +10
Agent interface10%107070even
Documentation and upkeep10%104349LFM3-Omni-2B +6
Negative events≤1500
TotalC 55.8/100C 61/100

Facts side by side

FactLBS-27BLFM3-Omni-2B
KindOpen-weight modelOpen-weight model
VendorinclusionAI (Ant Group)Liquid AI
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0 (the card's metadata and licence section; the LICENSE file sits in the GitHub repository inclusionAI/UI-Venus on its LBS branch, not in the Hugging Face repository)LFM Open License v1.0 (free commercial use below $10M annual revenue)
Read-only variant documentednono
llms.txtnoyes
Last release2026-10-262026-11-03
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked

How the scores have moved

Verdicts

LBS-27B

A 27B Qwen3.8 fine-tune for GUI grounding that zooms into screenshots over a few turns before naming a point, and inclusionAI says it also helps with fine detail in large images. It needs about 96 GB at BF16 and a client that runs its crop actions. Every result so far is inclusionAI's own, with no safety results or injection guidance.

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.

Before you call either

LBS-27B

  1. Serve with vllm serve inclusionAI/LBS-27B --tensor-parallel-size 4 --max-model-len 65536, which is what the card's wrapper script runs; keep the context at 32,768 or more for multi-turn images
  2. Build the system prompt with build_system_prompt from the LBS branch's zoomin_grounding_protocol.py, send the screenshot after image_path: <name>, and don't pass tools; the model answers in plain text
  3. Parse <action>crop_image(image_path=..., x1=..., y1=..., x2=..., y2=...)</action>, cut the crop yourself and return it with its mapping to the original image; allow at most two crops per turn and three per episode
  4. Read the final answer as [x.xx,y.yy] on a 0 to 1000 scale of the original image, and use your own executor to click
  5. Pass reasoning_effort as xhigh, medium or low only, since the template raises an error for high, and don't count on thinking_budget, which the template ignores
  6. Don't turn on MTP speculative decoding; the MTP weights aren't in the repository though config.json names one MTP layer

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

Questions

Which is better for AI agents, LBS-27B or LFM3-Omni-2B?

LFM3-Omni-2B scores 61 (C) on agent readiness against LBS-27B's 55.8 (C), and leads in 2 of 4 scored categories. LBS-27B leads on risk.

Other comparisons with LBS-27B or LFM3-Omni-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.