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

GLM-4.7-Flash vs LFM3-Omni-2B

GLM-4.7-Flash scores 63 (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 4969 open weights comparisons

Which one, for what

GLM-4.7-Flash B

Best for Agents and developers who want a small, permissively licensed tool-calling model on one 24 to 32 GB GPU or Mac, in almost any runtime

Ahead on

  • Risk, 55 against 40
  • Agent interface, 85 against 70

Watch for

No change to the files since 29 January 2026 and no zai-org reply on discussions since 31 January

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 28

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.

Documentation and upkeep LFM3-Omni-2B +21

GLM-4.7-Flash 28

The card covers architecture, parameters and languages and misses four of the seven items, for 8. Training data is 0, as the card describes none. The last change was on 1 February 2026 at the latest, within a year but past 180 days, for 5. Responsiveness is 5, since zai-org answered 6 of the 40 most recent discussions, all by 31 January, which is a few. Version policy is 5 for a first release with no files replaced, and file health is 5, as config.json and tokenizer_config.json disagree on context and a config report waits without a reply.

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.

Risk GLM-4.7-Flash +15

GLM-4.7-Flash 55

File safety is full, with safetensors only and the card loading it through Transformers' own code without remote code. Provenance is full, files in the zai-org organisation Z.ai links from GitHub with a SHA-256 for every shard. Safety evaluation and agent guidance are 0, as nothing is published on either. Licence risk is the full 15, since MIT adds no policy, threshold or changeable terms, though the repository carries no LICENSE file. The security programme is 0, with no security.txt, no SECURITY file and no advisories found.

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.

Agent interface GLM-4.7-Flash +15

GLM-4.7-Flash 85

A Jinja chat template sits in the repository, for 20. The tool-calling format is the full 25, because Z.ai itself names the glm47 parser for vLLM and SGLang, says tools are declared in OpenAI style and shows calls coming back as tool_calls. The template takes several calls in one turn, for 20. Structured output is 0, with nothing on the card and only the hosted API documented for JSON. Reasoning control is 10, thinking turned off per request with enable_thinking and the reasoning returned by the glm45 parser. Context is 10, 202,752 positions native with no rope scaling.

LFM3-Omni-2B 70

Chat template 20, chat_template.jinja in the repository (13,513 characters), with roles, images, video and audio, tools, deferred tools and tool results. 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 documents tool calling from spoken or written requests. Structured output 0, the card doesn't mention JSON or structured output for this model. Reasoning control 0, the card says this is a non-reasoning model and that enable_thinking=True is not supported, so there is no thinking to turn off or budget. Context 5, 32K tokens of input and output per the card. 20 + 25 + 20 + 0 + 0 + 5 = 70.

Score by category

CategoryWeight this runGLM-4.7-FlashLFM3-Omni-2BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%258080even
Risk20%205540GLM-4.7-Flash +15
Agent interface10%108570GLM-4.7-Flash +15
Documentation and upkeep10%102849LFM3-Omni-2B +21
Negative events≤1500
TotalB 63/100C 61/100

Facts side by side

FactGLM-4.7-FlashLFM3-Omni-2B
KindOpen-weight modelOpen-weight model
VendorZ.ai (Zhipu AI)Liquid AI
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceMITLFM Open License v1.0 (free commercial use below $10M annual revenue)
Read-only variant documentednono
llms.txtnoyes
Last release2026-01-292026-11-03
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviews2.8/5 (4)none

Verdicts

GLM-4.7-Flash

A small MIT-licensed mixture-of-experts model with about 3B active parameters, for local agent and coding work with several tool calls per turn and optional thinking. It runs in Ollama at about 23 GB and in nearly every common runtime. The main risk is neglect, with no changes or replies since early February and no safety results.

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

GLM-4.7-Flash

  1. On our reference machine start it with vllm serve zai-org/GLM-4.7-Flash --max-model-len 65536 --tool-call-parser glm47 --reasoning-parser glm45 --enable-auto-tool-choice --served-model-name glm-4.7-flash
  2. Or run ollama run glm-4.7-flash for the 19 GB q4_K_M build
  3. Without the glm47 and glm45 parsers, tool calls and reasoning come back as plain text
  4. Use a released vLLM (0.32.0 or later) or SGLang (0.5.22 or later); the card's nightly and pull-request builds date from January 2026
  5. Pass chat_template_kwargs: {"enable_thinking": false} for short tasks, since thinking is on by default
  6. Set clear_thinking: false to keep earlier reasoning in multi-turn agent work, as Z.ai does for τ²-Bench and Terminal Bench
  7. Set the context length yourself, since config.json allows 202,752 tokens and tokenizer_config.json says 128,000

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, GLM-4.7-Flash or LFM3-Omni-2B?

GLM-4.7-Flash scores 63 (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 GLM-4.7-Flash 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.