A 24B agent model that only wakes up 2B parameters at a time 🤖

Running an AI agent all day costs a lot of tokens. Before it does anything useful, a good agent plans, calls a tool, reads the result and thinks again. If every one of those reasoning tokens goes through a big model in the cloud, you pay for it in money, in latency and in privacy. That's why one release from last week caught my eye: Liquid AI's LFM2.5-24B-A2B, an open-weight reasoning model built specifically for agents that run on your own hardware.

What it is

LFM2.5-24B-A2B has 24 billion parameters in total, but it's a mixture-of-experts (MoE) model: for each token only about 2 billion of them are active. Each MoE block has 64 experts and routes every token to 4 of them. The architecture mixes gated short convolutions with grouped-query attention, the same hybrid as its predecessor LFM2-24B-A2B. New in this version is a context window of 131K tokens (up from 32K), and the vocabulary has doubled from 65K to 128K tokens, which helps with non-Latin scripts.

It's a reasoning-only model: it always writes out a chain of thought before it answers. Normally that makes a model slow and expensive. Here it doesn't hurt much, because each of those thinking tokens only touches 2B active parameters.

How they trained it

The training recipe is the part I find most interesting. Pre-training doubled from roughly 17T to roughly 33T tokens, followed by mid-training on reasoning, code, math and long-context data. Tool calls and multi-turn trajectories show up throughout. Post-training then has five stages: supervised fine-tuning, specializing teacher models, two rounds of on-policy distillation from those teachers (first on non-agentic tasks, then on agentic ones), and finally reinforcement learning inside real agent harnesses such as OpenClaw, Hermes Agent, Pi and OpenCode. So the model isn't only trained to call tools in theory. It practised in the same environments people actually use.

The numbers, honestly

Liquid AI compared it on 16 benchmarks with Qwen3.6-35B-A3B, Gemma-4-26B-A4B-it and Nemotron-3.5-Lightning, all of which are bigger. The strengths are clear:

  • LiveClaw: 48.09, compared with 38.19 for Qwen3.6-35B-A3B
  • AutomationBench: 27.69, more than three times the next-best model (8.72)
  • IFEval: 96.75, the best of the four, and it also leads on IFBench and Multi-IF

It's also fast: 184 tokens per second on an Apple M5 Max, 114 tok/s on a Ryzen AI Max+ 395, and over 21K output tokens per second at high concurrency on a single NVIDIA B300.

What I like is that the team is upfront about the weak spots. The bigger models still win on knowledge-heavy tests like GPQA Diamond (74.42 compared with 83.69 for Qwen) and on coding: SWE-Bench Verified is 51.0 compared with 66.2. Their own advice is to pair it with retrieval or web search for knowledge-heavy work. That's a sensible way to think about small models: let them reason and use tools, and let the facts come from outside.

Why this matters to me

For my homelab this is exactly the right direction. An agent that can run around the clock on a single machine, call tools reliably and keep data in the house is far more practical than one that needs a rack of GPUs or a cloud bill. It ships with support for llama.cpp, MLX, vLLM, SGLang and ONNX from day one, and it plugs into any OpenAI-compatible backend, so trying it out is a weekend project rather than a research one.

Small, focused, honest about its limits. That's the kind of open model progress I like to see.

Sources

Reacties

Populaire posts van deze blog

SpaceX just asked to fly Starship hundreds of times a year 🚀

AI that can actually "see" a crystal 🔬

Google's Deep Review wants to be the second pair of eyes on every long document 🔍