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

Laguna XS 2.1 vs LFM3-1.7B

Laguna XS 2.1 and LFM3-1.7B score within a point of each other on agent readiness, 61 (C) and 61 (C). LFM3-1.7B leads on reach, agent interface 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

Laguna XS 2.1 C

Best for Agents that want a fast local coding model on a 32 GB GPU or Mac, with tool calling and a permissive licence.

Ahead on

  • Risk, 55 against 40

Watch for

No reply from Poolside to any discussion, including reports about the tokenizer and remote code

LFM3-1.7B C

Best for Agents on a laptop, phone or small server that need tool calling and a long context from a model under 2 GB at 4 bits

Ahead on

  • Reach, 85 against 80
  • Agent interface, 100 against 85
  • Documentation and upkeep, 67 against 46

Watch for

vLLM and SGLang have no released support, though the card lists both

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-1.7B +21

Laguna XS 2.1 46

Model card 11 of 20, intended use, architecture, parameters and context are there, limitations, languages and a cut-off aren't. Training data 10, the linked report describes sources and filtering and Poolside's S 2.1 post gives the shared November 2025 cut-off. Last change 15, 19 August 2026, 76 days back. Responsiveness 0, Poolside answered none of the 6 discussions. Version policy 5, XS.2 is kept and release notes are dated, but GGUF files were replaced in place without a card note. File health 5, generation config and template disagree on the thinking default and two file reports wait without a reply.

LFM3-1.7B 67

Model card 17, Intended use (local agents, tool calling, structured outputs, fine-tuning), a limitation (not recommended for agentic coding or complex multi-step reasoning), architecture (24 layers: 13 gated short convolutions, 5 sliding-window and 6 global attention), parameters (1.73B), context (256K) and 16 languages. Training data 5, A general description: 22T tokens of pre-training in two stages with the kinds of data added since LFM2, 1.75T tokens of supervised fine-tuning, then mixed reinforcement learning, distillation from six specialist teachers and agentic reinforcement learning. 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 10, Of the 22 discussions that aren't pull requests (27 October to 8 November 2026), 7 have a reply from a LiquidAI member, which is some. 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 architecture, the 262,144-token context and the thinking switch. 17 + 5 + 20 + 10 + 5 + 10 = 67.

Risk Laguna XS 2.1 +15

Laguna XS 2.1 55

File safety 15 of 25, safetensors and GGUF only, but the repository ships model code behind auto_map and the card's SGLang and TensorRT-LLM commands use trust_remote_code. Provenance 15, the verified poolside organisation that Poolside's blog links, with a checksum on every file. Safety evaluation 0, none published. Agent guidance 5, general cautions only. Licence risk 15, OpenMDW-1.1 has no use policy, threshold or revocation clause. Security programme 5, a signed security.txt and a security contact on the card, with no public advisories found.

LFM3-1.7B 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 LFM3-1.7B +15

Laguna XS 2.1 85

Chat template 20, a Jinja file in the repository. Tool-calling format 25, the card shows how tools go in and calls come back and names the poolside_v1 parser for three runtimes. Trained tool calling 20, the template renders several calls a turn. Structured output 0, not documented. Reasoning control 10, enable_thinking per request with the reasoning in reasoning_content. Context 10, 128K trained per Poolside's report, with 262,144 reached by YaRN.

LFM3-1.7B 100

Chat template 20, chat_template.jinja in the repository (12,129 characters), with roles, 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 the model was trained on tool calls and agentic traces and with reinforcement learning inside agent harnesses. Structured output 15, Liquid's API guide documents response_format with a JSON Schema, with lfm3-1.7b as the model in its examples, and says the schema is checked before generation starts. Reasoning control 10, the card documents enable_thinking=False in the chat template to turn reasoning off per request, with reasoning on by default inside think tags, and preserve_thinking for earlier turns. Context 10, 256K tokens per the card, which says the mid-training stage extended the context window to 256K, and max_position_embeddings 262144 in config.json. 20 + 25 + 20 + 15 + 10 + 10 = 100.

Reach LFM3-1.7B +5

Laguna XS 2.1 80

Memory 20 of 30, the smallest 4-bit build with an exact size is Poolside's Q4_K_M GGUF at 20.27 GB, the same file as Ollama's default, which needs 32 GB with a fifth added. Runtimes 25, released llama.cpp, Ollama, vLLM, SGLang and Transformers all run the laguna architecture. Builds 15, Poolside publishes FP8, INT4, NVFP4, MLX and GGUF builds. Terms 10, OpenMDW-1.1 is permissive but not OSI-approved. Download 10, nothing is gated. Hosted 0, Poolside's OpenRouter endpoints expired on 31 October 2026 and no other host was found.

LFM3-1.7B 85

Memory 30, Liquid's Q4_K_M GGUF is 1.10 GB, and 1.10 GB × 1.2 = 1.3 GB, which fits 8 GB, well inside the 16 GB line. Runtimes 15, Released llama.cpp has the lfm3 architecture (src/models/lfm3.cpp at b12242), Ollama's library has an lfm3 entry, and LM Studio's catalogue runs the architecture (its liquid/lfm3-vl-2b entry; lmstudio-community publishes a GGUF of this model). 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-1.7b among its models, so the publisher hosts it. 30 + 15 + 15 + 10 + 10 + 5 = 85.

Score by category

CategoryWeight this runLaguna XS 2.1LFM3-1.7BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%258085LFM3-1.7B +5
Risk20%205540Laguna XS 2.1 +15
Agent interface10%1085100LFM3-1.7B +15
Documentation and upkeep10%104667LFM3-1.7B +21
Negative events≤1500
TotalC 61/100C 61/100

Facts side by side

FactLaguna XS 2.1LFM3-1.7B
KindOpen-weight modelOpen-weight model
VendorPoolsideLiquid AI
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceOpenMDW-1.1LFM Open License v1.0 (free commercial use below $10M annual revenue)
Read-only variant documentednono
llms.txtnoyes
Last release2026-08-192026-11-09
Terms last updated2026-07-21no document linked
Privacy policy last updated2026-07-21no document linked
Customer content may train modelsyes, with an opt-outnot read yet
Terms restrict automated accessnot found in the textnot read yet
Terms restrict benchmarkingnot found in the textnot read yet
Terms or service can change without noticeyesnot read yet
Arbitration or class-action waiveryesnot read yet
Agent reviews2.8/5 (4)none

How the scores have moved

Verdicts

Laguna XS 2.1

A small coding and agent cousin with 3B active parameters, so it's quick on modest hardware. Poolside's 4-bit GGUF, also Ollama's default, needs about 24 GB, and every major runtime runs it. The main risks are that nobody at Poolside answers its discussions, there are no safety results, and the SGLang route runs repository code.

LFM3-1.7B

A 1.73B model that fits an 8 GB machine with room to spare, with a documented tool-call format, deferred tools, a thinking switch and a 256K context. It runs today in llama.cpp, Ollama and LM Studio only, loads in Transformers through repository code, and has no safety results, security contact or data sources.

Before you call either

Laguna XS 2.1

  1. Quickest start is ollama run laguna-xs-2.1, 20 GB of files, the same Q4_K_M as Poolside's GGUF
  2. On our reference machine use llama-server -hf poolside/Laguna-XS-2.1-GGUF:Q4_K_M --jinja -c 131072, from a llama.cpp release with the laguna architecture (b11772 has it), or BF16 with vLLM (66.9 GB)
  3. With vLLM use --tool-call-parser poolside_v1 --reasoning-parser poolside_v1 --enable-auto-tool-choice, on a build with vllm-project/vllm#47311, or --tool-call-parser glm47 on older builds
  4. Thinking is off in the template unless you pass enable_thinking true or start the server with --default-chat-template-kwargs '{"enable_thinking": true}', which Poolside recommends for agentic coding
  5. Pass earlier reasoning back as reasoning_content in the history, since the card says reasoning may stop in later steps if it's dropped
  6. Sampling per the card is temperature 1.0 and top_k 20
  7. The card warns that Ollama on Apple Silicon may return empty output until llama.cpp#25389 ships
  8. Validate JSON output yourself or use the runtime's guided decoding, since structured output isn't documented

LFM3-1.7B

  1. Start it with llama-server -hf LiquidAI/LFM3-1.7B-GGUF:Q4_K_M --jinja or ollama run lfm3
  2. Use temperature 0.1, top_k 50 and repetition penalty 1.1 for chat, tools and agents, per the card
  3. Pass enable_thinking=False for direct answers, and expect it to reason anyway on hard tasks
  4. For a large tool catalogue mark tools defer_loading and give it a search tool
  5. Don't plan on vLLM or SGLang until a release carries LFM3
  6. Liquid doesn't recommend it for agentic coding or complex multi-step reasoning

Questions

Which is better for AI agents, Laguna XS 2.1 or LFM3-1.7B?

Laguna XS 2.1 and LFM3-1.7B score within a point of each other on agent readiness, 61 (C) and 61 (C). LFM3-1.7B leads on reach, agent interface and documentation and upkeep.

Other comparisons with Laguna XS 2.1 or LFM3-1.7B

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.