LFM 2.5-2.6B is Liquid AI's open-weight dense model built for on-device agentic workloads. Released on August 4, 2026 under the lfm1.0 license, it combines a 128K context window, native tool calling, and a sub-2.5 GB memory footprint for agents running continuously on laptops, phones, and single-GPU servers.
Core Features
- Native tool calling: Pythonic and JSON function calling, trained in real agent harnesses like Hermes Agent and OpenClaw.
- 128K context, 16 languages: 131,072 tokens, 128,000-token vocabulary, including Chinese and Japanese.
- On-device speed: 220 tok/s on Apple M5 Max, 113 tok/s on AMD Ryzen AI Max+ 395, 30 tok/s on phones, under 2.5 GB memory.
- Server throughput: One H100 serves about 1.3 billion tokens daily at high concurrency.
Model Specifications
| Specification | LFM 2.5-2.6B |
|---|---|
| Architecture | Dense hybrid, 30 layers (22 short convolution + 8 GQA), 2.69B total |
| Context | 131,072 tokens (128K); 128,000 vocabulary, 16 languages |
| Pretraining | ~34T tokens |
| Post-training | Two SFT rounds, teacher specialization, MOPD, agentic RL (GRPO) |
| Formats | GGUF, MLX, ONNX; llama.cpp, vLLM, SGLang, LM Studio |
| License | lfm1.0 (open weights) |
| Recommended quant | Q4KM (1.67 GB) |
Pricing
LFM 2.5-2.6B is free. Open weights on Hugging Face, no paid hosted API tier; your only cost is your own hardware.
Use Cases
- Always-on local agents: Agents that plan and call tools 24/7 on laptops or phones.
- Tool use and extraction: Native function calling for structured extraction and API orchestration.
- RAG and long context: The 128K window fits large document sets.
- High-throughput serving: About 1.3B tokens daily from one H100.
Not suited to agentic coding (its weak spot) or knowledge-intensive tasks beyond 2.6B parameters.
Advantages
- Leads its class on tool use and instruction following: Rivaling models four times its size via MOPD distillation and GRPO in real agent harnesses.
- Runs anywhere: 30 tok/s on a phone, 220 tok/s on Apple M5 Max; one stack spans mobile, desktop, and server.
- Deployment-ready: Day-one GGUF, MLX, ONNX builds plus llama.cpp, vLLM, SGLang, LM Studio.
- Cheap at scale: High per-GPU throughput keeps serving costs low.
Tips
- Use Q4KM: 1.67 GB, the recommended quality-footprint balance.
- Pair it with a real harness: Hermes Agent, OpenClaw, or Pi match its training loops.
- Skip it for coding agents: Choose a coding-focused model instead.
Conclusion
LFM 2.5-2.6B is a focused 2.6B agent engine: 128K context, native tool calling, and open weights that run almost anywhere. For agentic tool use, extraction, RAG, or long-context automation on local hardware, it is among the strongest in its class; for coding or deep world knowledge, look bigger.
Alternatives
- LFM 2.5 8B A1B: Liquid AI's larger hybrid MoE sibling.
- Qwen 3.8 27B: Bigger open-weight option with stronger general knowledge.
- Gemma 3: Google's open model family for on-device and single-GPU use.
Comments
No comments yet. Be the first to comment!
Related Tools
Kimi K3
www.kimi.com
Moonshot AI's open-weight 2.8T multimodal agentic model with 1M-token context, the world's first open 3T-class model rivaling closed frontier models.
Qwen3.8-2.4T-A95B
qwen.ai
Alibaba's flagship 2.4T MoE model with 95B active parameters, 1M-token context, native multimodal input, and top-ranked agentic performance — the largest Qwen ever.
NVIDIA Nemotron 3.5 Lightning 30B A3B
build.nvidia.com/nvidia/nemotron-3.5-lightning-30b-a3b
NVIDIA's efficient open-weight 30B MoE hybrid model with 3B active parameters, 1M-token context, and single-GPU deployment for local reasoning and coding.
Related Insights

Anthropic Subagent: The Multi-Agent Architecture Revolution
Deep dive into Anthropic multi-agent architecture design. Learn how Subagents break through context window limitations, achieve 90% performance improvements, and real-world applications in Claude Code.
Stop Cramming AI Assistants into Chat Boxes: Clawdbot Picked the Wrong Battlefield
Clawdbot is convenient, but putting it inside Slack or Discord was the wrong design choice from day one. Chat tools are not for operating tasks, and AI isn't for chatting.
After I Connected Obsidian to OpenClaw, It Started Helping Me Make Decisions
Once Obsidian stopped being just a place to store notes and started working with OpenClaw, it began helping me organize context, connect information, and improve real decisions.