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

LFM2.5-2.6B vs North Mini Code 1.0

North Mini Code 1.0 scores 61 (C) on agent readiness against LFM2.5-2.6B's 50.3 (D), and leads in 2 of 4 scored categories. LFM2.5-2.6B 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

LFM2.5-2.6B D

Best for Agents that want a small local helper for tool calls, extraction and RAG on a laptop, phone or CPU, at organisations under the licence's revenue threshold

Ahead on

  • Reach, 90 against 85
  • Documentation and upkeep, 57 against 36

Watch for

Liquid lists it as deprecated, replaced by LFM3-1.7B; deprecated models stay downloadable but get no further updates

North Mini Code 1.0 C

Best for Developers who want a coding agent on their own GPU with a permissive licence

Ahead on

  • Risk, 60 against 50
  • Agent interface, 85 against 75

Watch for

No limitations, safety results, languages or data description on the card

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 LFM2.5-2.6B +21

LFM2.5-2.6B 57

The model card earns 17, with everything but a knowledge cut-off. Training data earns 5 for a general description without a cut-off. The last change earns 20, a card commit on 3 November 2026 naming LFM3-1.7B as the new version. Responsiveness earns 5, with Liquid replies in 2 of 16 discussions. Version policy earns 5, as Liquid now lists the model as deprecated with a replacement but no date. File health earns 5, since the files agree but a report about the card waits without a reply.

North Mini Code 1.0 36

Model card 11, Intended use, the architecture, the parameters and the context are on the card. Training data 0, the card gives the training method and nothing about the data. Last change 10, the main repository last changed on 15 June 2026 (outdated chat templates removed), 148 days before this check, and the draft model's repository on 29 July, 104 days. Responsiveness 0, none of the 11 most recent discussions that aren't pull requests (7 June to 6 November 2026) has a reply from a CohereLabs member, counted on 10 November by author flags and dates with a script, text not read. Version policy 5, A first release, with each build in its own repository. File health 10, Config, template and card agree on the architecture, and the June commit that removed broken templates says so. 11 + 0 + 10 + 0 + 5 + 10 = 36.

Risk North Mini Code 1.0 +10

LFM2.5-2.6B 50

File safety earns 25, safetensors and GGUF only, and nothing from the repository runs to load it or build prompts. Provenance earns 15, files in the LiquidAI organisation Liquid links to, with a checksum for every file. Safety evaluation and agent guidance earn nothing, since Liquid publishes neither. Licence risk earns 10, losing 5 for the revenue threshold, with no use policy and no change since release. The security programme earns nothing, since no security.txt, disclosure policy or security contact was found.

North Mini Code 1.0 60

File safety 25, safetensors only, no .bin, .pt or .pth files and no Python in the repository. Provenance 15, the files sit in Cohere's verified CohereLabs organisation, which cohere.com links to per our other Cohere listings (10). Safety evaluation 0, no safety results on the card. Agent guidance 0, the card has no limitations or safety section, and nothing on prompt injection, instruction priority or what the model refuses. Licence risk 15, Apache 2.0 has no use policy, threshold or change clause. Security programme 5, Cohere's trust centre holds a responsible disclosure policy with a bug bounty, as recorded on our Cohere listings (5). 25 + 15 + 0 + 0 + 15 + 5 = 60.

Agent interface North Mini Code 1.0 +10

LFM2.5-2.6B 75

The chat template earns 20 for chat_template.jinja in the repository. The tool-calling format earns 25, as Liquid's card and tool-use page say how tools go in and how calls come back, and its vLLM and SGLang pages name the lfm2 parser. Trained tool calling earns 20, with several calls in one Python list and agentic RL inside agent harnesses. Structured output earns nothing, as JSON output isn't documented for the model. Reasoning control earns nothing, since the model always thinks. Context earns 10 for 131,072 tokens trained.

North Mini Code 1.0 85

Chat template 20, chat_template.jinja in the repository (12,397 characters). Tool-calling format 25, the card documents how tools are declared (JSON schema through the chat template), how the call and its thinking go back into the history and how results are appended, and names the cohere_command4 tool-call parser for vLLM, which released vLLM has. Trained tool calling 20, the card says the model was specifically trained with tool-use capabilities for agentic coding, with reinforcement learning on verifiable tasks, and the template renders every call in a turn with thinking between them. Structured output 0, JSON schema is for describing tools. Reasoning control 10, the template has a reasoning_effort setting, and the card names the cohere_command4 reasoning parser, which returns thinking apart from the answer. Context 10, 256K tokens per the card, with 64K of output, and 500,000 positions in config.json. 20 + 25 + 20 + 0 + 10 + 10 = 85.

Reach LFM2.5-2.6B +5

LFM2.5-2.6B 90

Memory earns the full 30, since Liquid's own 4-bit GGUF is 1.59 GB and fits 8 GB with room to spare. Runtimes earn 25, with the lfm2 architecture in released llama.cpp, vLLM, SGLang and Transformers, and in Ollama through the llama.cpp version it pins. Builds earn 15 for Liquid's own GGUF, MLX and ONNX builds at many precisions. Terms earn 10, a custom licence that is free for commercial use under $10M of annual revenue. Download earns 10, with no gate. Hosted earns nothing, as Hugging Face maps no inference provider and Liquid's docs list no hosted API for it.

North Mini Code 1.0 85

Memory 25, the smallest build from Cohere is the w4a16 repository, 19.38 GB, and 19.38 GB × 1.2 = 23.3 GB, within 24 GB. Unsloth's GGUF isn't read for this line. Runtimes 20, Released vLLM 0.33.0, SGLang 0.5.23 and Transformers 5.22.2 have the cohere2_moe model, and llama.cpp b12242 has the cohere2moe architecture. Builds 15, Quantised builds from Cohere at two precisions, FP8 and 4-bit weights (w4a16), each in its own repository. Terms 15, Apache 2.0 in the metadata and on the card, an OSI licence with nothing added. Download 10, the Hub API reports gated false for the model and its builds on 10 November 2026, so the files download with no account and nothing to accept. Hosted 0, Hugging Face maps no inference provider to it. 25 + 20 + 15 + 15 + 10 + 0 = 85.

Score by category

CategoryWeight this runLFM2.5-2.6BNorth Mini Code 1.0Edge
Capability35%pendingpendingpendingnot scored in this run
Reach25%259085LFM2.5-2.6B +5
Risk20%205060North Mini Code 1.0 +10
Agent interface10%107585North Mini Code 1.0 +10
Documentation and upkeep10%105736LFM2.5-2.6B +21
Negative events≤1500
TotalD 50.3/100C 61/100

Facts side by side

FactLFM2.5-2.6BNorth Mini Code 1.0
KindOpen-weight modelOpen-weight model
VendorLiquid AICohere
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-07-29
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviews2.5/5 (4)none

How the scores have moved

Verdicts

LFM2.5-2.6B

A small, fast model for tool calls, extraction and long-context steps on a laptop or phone, which Liquid now lists as deprecated in favour of LFM3-1.7B. Liquid's own 4-bit build is 1.6 GB and five common runtimes run it. It always thinks, and organisations over $10M of revenue need another licence. There are no safety results or security contact.

North Mini Code 1.0

A coding agent model that fits one 24 GB GPU at 4 bits, trained for tool use, with a 256K context, Apache 2.0 and four released runtimes. It's a research release and reads like one: nothing on limitations, safety or data, the card's run instructions are out of date, and Cohere hasn't answered a question on the repository.

Before you call either

LFM2.5-2.6B

  1. Quickest start is ollama run LiquidAI/lfm2.5-2.6b, 1.7 GB, or llama-cli -hf LiquidAI/LFM2.5-2.6B-GGUF
  2. With vLLM or SGLang pass --tool-call-parser lfm2; for vLLM add --reasoning-parser qwen3 so the thinking comes back separately
  3. Sample at temperature 0.1, top_k 50 and repetition_penalty 1.1, as the card and generation_config.json set
  4. Put tools in the system prompt as List of tools: [...] JSON, or pass tools to apply_chat_template; calls come back as a Python list of function calls, and the system prompt can ask for JSON calls instead
  5. Leave max_tokens unset or generous, since a low cap cuts the reasoning off mid-thought
  6. Earlier thinking is dropped from the prompt unless preserve_thinking is true
  7. Liquid's 328M LFM2.5-2.6B-DSpark drafter speeds decoding about 2.6 times in SGLang and on Apple silicon, per Liquid
  8. Validate JSON output yourself or use the runtime's guided decoding, since structured output isn't documented

North Mini Code 1.0

  1. Serve it with vLLM 0.33.0 or later and --tool-call-parser cohere_command4 --reasoning-parser cohere_command4 --enable-auto-tool-choice, with cohere_melody installed
  2. Pass the model's thinking back with its tool calls on every turn. The card says results drop without it
  3. Describe tools in JSON schema and append tool results as a dictionary with the tool role
  4. Use temperature 1.0 and top_p 0.95
  5. For llama.cpp the GGUF files are Unsloth's or bartowski's conversions, not Cohere's
  6. It's text only. Don't send images

Questions

Which is better for AI agents, LFM2.5-2.6B or North Mini Code 1.0?

North Mini Code 1.0 scores 61 (C) on agent readiness against LFM2.5-2.6B's 50.3 (D), and leads in 2 of 4 scored categories. LFM2.5-2.6B leads on reach and documentation and upkeep.

Other comparisons with LFM2.5-2.6B or North Mini Code 1.0

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.