Skip to main content
Liquid AI's new open weights model for on-device agents, depicted by a glowing brain icon on a smartphone.

Editorial illustration for Liquid AI Releases Open Weights Model for On-Device Agents

Liquid AI Releases 2.6B On-Device Agent Model

Liquid AI Releases Open Weights Model for On-Device Agents

4 min read

Liquid AI put out LFM2.5-2.6B this week, a model built to run agentic workloads entirely on local hardware, no server round-trip required. At 2.69 billion parameters, it fits on phones, laptops, PCs, and robots, with a 131,072-token context window and a 128,000-token vocabulary behind it. Pre-training drew on roughly 34 trillion tokens, and the company shipped two versions: LFM2.5-2.6B-Base for developers who want to fine-tune, and a post-trained LFM2.5-2.6B tuned specifically for planning, tool calls, and multi-step tasks.

The pitch is straightforward: since inference happens on the device itself, prompts never touch a third-party API, and each run costs close to nothing to execute. Liquid AI says the model holds its own against systems roughly four times its size on tool-use and instruction-following benchmarks, a claim that matters most for anyone trying to cut inference costs or keep data off outside servers entirely. Both checkpoints are live on Hugging Face under the lfm1.0 license, with weights available in native, GGUF, MLX, and ONNX formats. That range of formats is the detail worth sitting with before getting into how it actually performs.

Liquid AI released LFM2.5-2.6B, an agentic model that runs entirely on-device. It plans, calls tools, and works through multi-step tasks on phones, laptops, PCs, and robots.

Why this matters

For developers building on phones or edge hardware, LFM2.5-2.6B is worth testing this week rather than filing away for later. A 2.69B-parameter model with a 128K context window and open weights removes two of the usual excuses for skipping on-device agents: cloud latency and data leaving the device. Liquid AI shipping both a base checkpoint and a post-trained agentic version gives founders a real choice between fine-tuning from scratch or deploying something already tuned for tool calling and RAG.

The 34-trillion-token pre-training run signals this isn't a toy demo meant to score well on a leaderboard and nothing else; it's aimed at document triage, invoice extraction, and robotics command parsing, tasks with actual production stakes. Researchers should still push on the harder question: how does a 2.6B model handle long-context reasoning compared to larger cloud models when the task gets messy rather than clean? Liquid AI's own list of "recommended" use cases reads like a roadmap for where they expect early adopters to find the cracks first.

Common Questions Answered

What are the key specifications of Liquid AI's LFM2.5-2.6B model?

LFM2.5-2.6B is a 2.69 billion parameter model with a 131,072-token context window and 128,000-token vocabulary, pre-trained on approximately 34 trillion tokens. The model is designed to run entirely on-device across phones, laptops, PCs, and robots without requiring server round-trips, making it suitable for edge hardware deployment.

What are the two versions of LFM2.5-2.6B that Liquid AI released?

Liquid AI shipped LFM2.5-2.6B-Base for developers who want to fine-tune the model from scratch, and a post-trained LFM2.5-2.6B specifically tuned for planning and tool calling. This dual-version approach gives developers the flexibility to either customize the base model or deploy the pre-configured agentic version immediately.

How does LFM2.5-2.6B enable on-device agentic workloads?

The model can plan, call tools, and work through multi-step tasks entirely on local hardware without cloud latency or data transmission to external servers. With its 128K context window and open weights, developers can build agents that maintain privacy and reduce latency by processing tasks directly on edge devices like phones and robots.

Why is the open weights release of LFM2.5-2.6B significant for developers?

The open weights model removes two major barriers to on-device agent development: cloud latency and data privacy concerns from sending information to external servers. Developers can now test and deploy agentic capabilities on edge hardware without relying on proprietary cloud infrastructure, making it practical for applications requiring real-time processing and data confidentiality.

LIVE05:54Liquid AI Releases Open Weights Model for On-Device Agents