LFM3-VL-2B vs Qwen3-Coder-Next

LFM3-VL-2B 77

Model card 17, Intended use (questions about video, documents, charts and app screens, finding objects, spatial reasoning), a limitation (not recommended for coding, multi-turn conversations or complex reasoning), architecture (language model, 14-layer vision encoder and projector), parameters (1.92B), context (128K) and 16 languages. Training data 5, A general description: the base's 22T tokens of pre-training with the kinds of data added since LFM2, then vision mid-training on image and video data, supervised fine-tuning, vision reinforcement learning and distillation. 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 20, Of the 5 discussions that aren't pull requests (27 to 31 October 2026), 3 have a reply from a LiquidAI member, which is most. 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_vl architecture, the 128,000-token context and the vision settings in processor_config.json. 17 + 5 + 20 + 20 + 5 + 10 = 77.

Qwen3-Coder-Next 41

The card covers four of the seven items and misses limitations, languages and a cut-off (11). The technical report names the data sources, the cut-off and the filtering with some sizes (15). The files last changed on 3 February 2026 (4 February in the GGUF repository), 274 days ago, within a year (5). Alibaba's staff answered none of the 40 discussions; the one reply from a Qwen organisation member is not the publisher's (0), and GitHub issues couldn't be counted. It's a first release (5), and reports of a broken shipped parser and the missing licence wait unanswered (5). 11+15+5+0+5+5 = 41.

LFM3-VL-2B 90

Chat template 20, chat_template.jinja in the repository (12,129 characters), with roles, images and video, 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 its fine-tuning mix included tool calling and agentic traces. Structured output 5, the card's vLLM and SGLang commands set a structured-output backend and its fine-tuning table has a JSON extraction notebook, but nothing says how to ask this model for JSON. Liquid's API guide documents response_format with lfm3-1.7b as its example. Reasoning control 10, Liquid's chat-template page documents enable_thinking=False in apply_chat_template for LFM3, with reasoning on by default inside think tags, and the card documents preserve_thinking and reports a no-thinking configuration in its benchmarks. Context 10, 128K tokens of input and output per the card, and max_position_embeddings 128000 for the language model in config.json. 20 + 25 + 20 + 5 + 10 + 10 = 90.

Qwen3-Coder-Next 75

The template ships in the repository (20). Tool calling is the model's strength, and Alibaba documents how tools are declared, names and ships the qwen3_coder parser and describes the format in its report (25), with several calls per turn in a model trained on 21 harness formats (20). Context is 262,144 tokens native (10). Structured output scores 0, as nothing documents JSON output, and reasoning control scores 0 because the model has no thinking mode to control.

LFM3-VL-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-Coder-Next 50

Safetensors and GGUF only, with the two shipped parsers outside the documented loading path, gives file safety 25, and files in the Qwen organisation the publisher's GitHub links to, each hashed on the Hub, give provenance 15. Licence risk loses 5 because the card's licence link is broken and no LICENSE file exists anywhere. Safety evaluation, agent guidance and a security programme score 0, since the report's cybersecurity appendix measures skills rather than safe behaviour, nothing guides agent use and no reporting route was found.