Skip to main content

Deploy Local Agents Everywhere: Liquid AI Releases LFM2.5-2.6B with 128K Context and Zero Marginal Cost

Ilustrační obrázek
Liquid AI has released LFM2.5-2.6B and its foundation counterpart LFM2.5-2.6B-Base on Hugging Face, establishing a new benchmark for compact, edge-ready artificial intelligence. Featuring a hybrid architecture combining gated short convolutions with grouped-query attention, the 2.69-billion parameter model delivers native 128K context windows, real-time tool calling, and speeds up to 220 tokens per second on consumer hardware—offering complete data privacy and zero marginal inference costs.

Bringing High-Speed Agentic Capabilities Directly to the Edge

The landscape of local artificial intelligence marked a significant milestone on August 4, 2026, when Liquid AI officially published weights for LFM2.5-2.6B and LFM2.5-2.6B-Base. Coming shortly after the late-July rollout of the LFM2.5-Encoders series, this new release targets on-device local agentic workloads where latency, privacy, and operational costs have traditionally presented serious bottlenecks.

Despite packing 2.69 billion parameters pre-trained on approximately 34 trillion tokens, LFM2.5-2.6B maintains a compact memory footprint under 2.5 GB. This lightweight memory profile enables developers across Europe and worldwide to deploy fully autonomous AI agents directly onto standard laptop CPUs, consumer GPUs, and modern mobile smartphones without relying on external cloud APIs.

Under the Hood: Architecture and Post-Training Pipeline

Unlike traditional monolithic dense transformers, LFM2.5-2.6B leverages a hybrid architectural blueprint. By marrying gated short convolutions—which excel at linear-time sequence processing and low-memory state updates—with grouped-query attention (GQA), the model achieves high generation throughput while maintaining long-range reasoning over its native 128K token context window.

To support international and non-Latin scripts cleanly, Liquid AI executed an in-place vocabulary expansion, increasing the model's tokenizer capacity to 128,000 tokens. This update drastically improves tokenization efficiency for European languages, reducing overall token counts per prompt compared to older compact models.

The intelligence behind LFM2.5-2.6B's agentic capabilities stems from a specialized four-stage post-training pipeline designed specifically for function execution and tool interactions:

  • Supervised Fine-Tuning (SFT): Establishes base instruction-following and task alignment across general datasets.
  • Teacher Specialization: Distills complex domain knowledge from larger frontier models into targeted sub-domains.
  • Multi-Domain On-Policy Distillation (MOPD): Refines internal decision paths based on real-time execution feedback.
  • Agentic Reinforcement Learning (Agentic RL): Optimizes multi-step reasoning, self-correction, and tool-calling precision.

On-Device Speed and Benchmark Benchmarking

In empirical performance testing, LFM2.5-2.6B delivers remarkable inference throughput across consumer and server hardware. On Apple M5 Max silicon, the model achieves processing speeds of 220 tokens per second. On the AMD Ryzen AI Max+ 395 platform, it hits 113 tokens per second, while maintaining around 30 tokens per second on standard flagship smartphones.

For high-density enterprise deployments, a single NVIDIA H100 GPU hosting LFM2.5-2.6B can generate up to approximately 15,000 output tokens per second at high concurrency, translating to a capacity of roughly 1.3 billion tokens generated daily on one accelerator card.

As evaluated across recognized industry benchmarks, LFM2.5-2.6B outperforms many existing small language models in structured tool execution and instruction adherence:

  • BFCLv4 (Berkeley Function Calling Leaderboard): 56.88
  • IFStruct (Instruction Structure Following): 85.49
  • ToolSandbox: 77.83
  • PinchBench: 68.22
  • Claw-Eval (English Average): 62.85

As observed in our hardware testing protocols at the AI Arena lab, running models sub-3GB locally eliminates initial network handshakes, resulting in near-instantaneous first-token latency crucial for real-time assistant applications.

Economic Analysis: Edge Deployment vs Cloud API Costs

For organizations building continuous multi-step agentic workflows, API billing can rapidly become the dominant operational expense. Running automated loops—where an agent repeatedly queries external tools, inspects output files, and revises internal states—generates millions of input and output tokens per day.

Deploying LFM2.5-2.6B locally brings marginal per-token inference costs down to $0.00 (€0.00), shifting expenses purely to local electricity and existing hardware amortization. The cost differential against cloud hosted alternatives highlights the scale of potential savings:

Model Developer / Provider Input Price (1M Tokens) Output Price (1M Tokens) Deployment Target
LFM2.5-2.6B Liquid AI $0.00 (€0.00) $0.00 (€0.00) Local / On-Device / Self-Hosted
DeepSeek-V4-Flash DeepSeek $0.14 (€0.13) $0.28 (€0.26) Cloud API / Open Weights
Gemini 3.6 Flash Google DeepMind $1.50 (€1.38) $7.50 (€6.90) Cloud API
Mistral Medium 3.5 Mistral AI $1.50 (€1.38) $7.50 (€6.90) Cloud API / Open Weights
Grok 4.5 xAI $2.00 (€1.84) $6.00 (€5.52) Cloud API
Kimi K3 Moonshot AI $3.00 (€2.76) $15.00 (€13.80) Cloud API / Open Weights
GPT-5.6 Sol OpenAI $5.00 (€4.60) $30.00 (€27.60) Cloud API
Claude Opus 5 Anthropic $5.00 (€4.60) $25.00 (€23.00) Cloud API

Consider an enterprise running a swarm of local office assistants processing 20 million input tokens and 5 million output tokens daily. Using standard cloud frontier tier APIs like GPT-5.6 Sol, that workload costs $250 (~€230) per day, accumulating to over €6,900 monthly. Running LFM2.5-2.6B locally on standard workstations reduces recurring vendor bills to zero while preserving predictable performance.

The European Angle: GDPR Compliance and Regulatory Context

For European companies and public sector entities, local model deployment offers strategic regulatory advantages. Under the General Data Protection Regulation (GDPR), transmitting sensitive customer records or proprietary source code to overseas cloud endpoints introduces data protection friction and compliance overhead.

Because LFM2.5-2.6B operates entirely within an organization’s local perimeter, data never leaves the physical device or local server network. This self-contained processing satisfies strict data sovereignty requirements and simplifies enterprise risk management.

Furthermore, the regulatory backdrop in Europe has recently clarified. Direct enforcement by the European Commission's AI Office took effect on August 2, 2026, establishing binding governance standards, signed Codes of Practice, and mandatory transparency obligations for General-Purpose AI (GPAI) providers—including watermarking and machine-readable content labeling. Meanwhile, following the adoption of the AI Omnibus amendment in June 2026 (in force since July 2026), full compliance deadlines for Annex III high-risk AI systems have been deferred to December 2, 2027. Open-weight models like LFM2.5-2.6B give developers total transparency to audit model parameters and implement local compliance controls directly.

Native Integration with Agent Frameworks

To ensure frictionless adoption, LFM2.5-2.6B includes out-of-the-box support for popular local agent harnesses, including OpenClaw, Hermes Agent, and Pi. Developers can bind local API hooks, system commands, and custom Python functions directly into the model's tool-calling loop.

Whether automating local document processing, handling coding tasks within an IDE, or running offline diagnostic bots on embedded hardware, LFM2.5-2.6B demonstrates that state-of-the-art agentic automation no longer requires a constant connection to cloud hyperscalers.

Is LFM2.5-2.6B freely available for developers in the European Union?

Yes, LFM2.5-2.6B and LFM2.5-2.6B-Base were officially released on Hugging Face on August 4, 2026. The weights are globally available to download and run locally without regional geo-blocking or API access restrictions.

What hardware is required to run LFM2.5-2.6B locally?

Because the model requires less than 2.5 GB of memory, it runs comfortably on modern laptops (such as Apple Silicon or AMD Ryzen processors), standard desktop GPUs, and recent flagship smartphones.

How does on-device agent execution benefit GDPR compliance?

By executing function calls and context processing on local hardware, sensitive user data, system logs, and corporate code never leave your device or local network, eliminating cross-border data transfer risks under GDPR.

X

Don't miss out!

Subscribe for the latest news and updates.