Liquid AI has unveiled LFM2.5-24B-A2B, a Mixture-of-Experts (MoE) reasoning model that activates only 2B of its 24B parameters per token. According to an announcement published on the Hugging Face blog dated October 13, 2026, the model is designed to perform explicit thinking before producing an answer, invoke tools, and execute multi-step tasks within agent harnesses such as OpenClaw, Hermes Agent, Pi, and OpenCode. Because active parameters are limited to 2B per token, the per-inference-token cost is low, positioning the model as an on-device AI option for continuously running agents on self-owned hardware.
Architecture: 40 layers, 64 experts, hybrid attention
LFM2.5-24B-A2B inherits the LFM2-24B-A2B design with 40 layers, 64 experts per MoE block, and top-4 routing, retaining the same hybrid attention of gated short convolutions and GQA (Grouped Query Attention). The context window has been expanded from 32K to 131K tokens, and the tokenizer’s vocabulary has grown from 65K to 128K, improving non-Latin tokenization. Unlike LFM2-24B-A2B, it operates as a reasoning-only model and produces an explicit Chain of Thought before its final answer.
Training pipeline: 33T pre-training and 5-stage post-training
Pre-training token count has increased from approximately 17T to approximately 33T. Mid-training consists of 2T tokens at 32K context weighted toward reasoning, math, code, instruction following, and multilingual text, plus 300B tokens at 131K context weighted toward long-context data, with tool-calling and multi-turn trajectories appearing across both stages. Post-training proceeds in five stages: ① supervised fine-tuning (SFT); ② Multi-domain On-Policy Distillation (MOPD) non-agent stage, distilling expert models into non-agent tasks; ③ MOPD agent stage, distilling agentic tasks; ④ agentic reinforcement learning (training inside the agent harness); ⑤ follow-up fine-tuning.
Agent performance: #1 in 5 tool-use and 3 instruction-following benchmarks
Evaluation was conducted with vLLM, comparing against Qwen3.6-35B-A3B, Gemma-4-26B-A4B-it, and Nemotron-3.5-Lightning across 16 benchmarks spanning tool use, agentic workflow, knowledge, instruction following, math, and coding. Despite being the smallest model in the group, LFM2.5-24B-A2B delivered competitive performance against MoEs with roughly 50% more total and active parameters. Among the eight tool-use and agentic benchmarks, it ranked first or tied for first on five — AutomationBench, BFCLv4, ToolSandbox, LiveClaw, and τ³-Bench Banking — and on AutomationBench it scored more than three times the next-ranked model. On LiveClaw it scored 48.09, ahead of Qwen3.6-35B-A3B’s 38.19, and it also took first place across all three instruction-following benchmarks. On the other hand, larger models maintained their edge on knowledge-centric benchmarks such as GPQA Diamond, HLE, and AA-Omniscience, and on coding benchmarks such as SWE-Bench Verified (OpenCode) and SciCode.
Inference speed: 184 tok/s on M5 Max, 21K tok/s on a single B300
The model is supported out of the gate on llama.cpp, MLX, vLLM, SGLang, and ONNX. On edge inference, it recorded decoding speeds of 184 tokens/s on Apple M5 Max and 114 tokens/s on Ryzen AI Max+ 395, while using the least memory — up to 1.7× faster than the next-ranked model. On GPU inference, a single NVIDIA B300 broke through 21K output tokens/s under high concurrency, delivering the fastest speed in its size class.
| Benchmark / Environment | LFM2.5-24B-A2B | Comparison |
|---|---|---|
| LiveClaw (agentic composite) | 48.09 | Qwen3.6-35B-A3B 38.19 |
| Edge decoding (Apple M5 Max) | 184 tokens/s | Up to 1.7× next-ranked |
| Edge decoding (Ryzen AI Max+ 395) | 114 tokens/s | Up to 1.7× next-ranked |
| Datacenter GPU (single B300) | 21K tokens/s (high concurrency) | Best in class |
Practical integration steps and agent harness linkage
The model is connected by serving it locally as an OpenAI-compatible backend and then pointing an agent harness at it. It is loaded through AutoModelForCausalLM in transformers 5.0.0 or later, with device_map=auto, dtype=bfloat16, and the flash_attention_2 option on compatible GPUs. In Hermes Agent, model.provider is set to custom, model.base_url points to the local OpenAI-compatible endpoint, and model.context_length is set to 131072 to enforce tool use. Default ports per serving backend are 8080 for llama.cpp and MLX, 8000 for vLLM, 30000 for SGLang, and 1234 for LM Studio. Because they share the same OpenAI-compatible interface, the same procedure can launch an agent on laptop-class edge devices such as the M5 Max, extending on-device AI applicability from data centers to personal devices.
Limitations and implications
In knowledge- and coding-oriented workflows, larger models still hold the advantage, and combining RAG or web search is recommended. The combination of 131K context and a 2B-per-token active parameter structure targets on-device AI scenarios that process tool calls and multi-step reasoning locally without external API dependencies. With both LFM2.5-24B-A2B and LFM2.5-24B-A2B-Base released as open weights on Hugging Face, the model is regarded as worth immediate review by teams that want to operate private agents on their own hardware.
Reference
This article was prepared by checking the following source: Hugging Face Blog — Run fast, private agents on-device with LFM2.5-24B-A2B

Leave a Reply