Excited to roll out LFM 3 to replace it, looks like a big step up. Right now LFM 2.6 gets trustworthy annotations on just over 40% of data points. Just waiting for these to get into LocalAI.
Excited to roll out LFM 3 to replace it, looks like a big step up. Right now LFM 2.6 gets trustworthy annotations on just over 40% of data points. Just waiting for these to get into LocalAI.
This seems interesting, but if anyone else is also doing a similar thing, I'd appreciate tips on how to approach it. So far, I think I have some small RAG model in a demo or the very small qwen models. I think fine tuning seems interesting too. Some of the decision models applied in layers (like a binary search on a pre-generated corpus) could be fast enough to help too?
idk too many options, i'm sure this is a solved problem lol
Would be a fun experiment.
1. I were building for my work laptop (M4 Max, 36GB RAM)
2. I had a batched use cases (transcribing + making action items for all meetings in a day)
I would use the LFM3-Audio-2B for ASR (audio -> text transcript) and then LFM3-1.7B for extracting particular action items and adding them to my tool of choice (Linear, Jira, Notes app, etc).
If you can fine-tune (100+ labeled samples, and a GPU), you likely can fine-tune LFM3-Audio-2B for audio -> action items in a single step.
> However, the instructions say I must use available tools when answering questions.
On "What animal lays the biggest egg?" with no system prompt
I assume this is something baked into the model through lots of RL with tool use?
The full request was
``` {"messages":[{"content":"What animal lays the biggest egg?","role":"user"}],"return_progress":true,"sse_ping_interval":1,"stream":true,"tools":[{"function":{"description":"Returns the current local date and time in ISO 8601 format, with the IANA time zone name","name":"get_datetime","parameters":{"properties":{},"required":[],"type":"object"}},"type":"function"},{"function":{"description":"Get runtime info (OS name), may call when user asks about local files or shell commands","name":"get_info","parameters":{"properties":{},"required":[],"type":"object"}},"type":"function"}],"reasoning_format":"auto","reasoning_control":true,"backend_sampling":false,"timings_per_token":true} ```
Disabling tools removes the bit about mentioning instructions.
Just an interesting detail I noticed.
Do y'all have any penalty/regularization w.r.t. reasoning traces or is it pure SFT -> RL?
SFT -> RL. In our fine-tuning notebooks, we typically say that rollouts that go past the max context length (too much reasoning) get 0 reward, so there is slight pressure for shorter reasoning, but I don't think we have strong regularization. I think the agreed-upon recipe is to first make the model smarter (longer reasoning), then teach it to reason faster/denser.
What makes it cool? What should make me go "oh yeah let's go"?
From what I can see by skimming the document, I would assume "something something specialized use-cases", but what does that mean? And what does it mean assuming I have attention deficit?
If you want to do local classification/image processing, I think the d1-2B is amazing, it can run on 1GB of unified RAM.
Now that it's released and I have weekends off again, I'm going to play with the VL-2B model and the d1-2B and see if I can prompt it to control a small Lego robot arm like this https://bricksrl.github.io/ProjectPage/
If you like agents, I think the 1.7B is very strong for its size and can be used to automate small stuff like classifying emails, cleaning your downloads folder, etc.
It can also be fine-tuned for specific use cases with SFT/DPO/GRPO. The blog post talks about fine-tuning for wind-turbine classification. If there's things you want to automate, but GPT-6-Luna is not strong enough, and bigger models are too expensive, you might fine-tune one of the LFM3 models and use it locally for repetitive tasks.
In other words: Should I select the model that matches my desired capability set or just use Omni?
It's a goal of ours to continue unifying training across modalities so that there is truly one model, instead of just this shared pre-trained backbone.
I'm curious if this model would be useful for OCR or at least text documents parsing (PDF, DOCX, etc.), what do you think?
In the past I've noticed that some LFM were way better at moderation than much larger models. Not necessarily prejudging what is acceptable, but allowing you to interrogate content with a series of questions to customize the moderation. Other models I tested were far worse.
Decision models are like the next optimization in that direction, but none of the benchmarks for the popular models ever show how good they are at tasks like content moderation. The smaller and more efficient we can get that workload, the more that it can simply be on by default in a lot of use cases without feeling like you're giving up a lot of performance, creative freedom or accuracy. You can't have a high number of false positives or people would rather take control back.
We need local content moderation to be cool, efficient, accurate and configurable so that people can get the higher quality results which unsafe models tend to produce, while filtering out the unsafe results fast enough that it can even be done in an agentic way and fed back into the model to steer its results.
It's mediatek NPU claims to handle ONNX. That plus the 12GB ram makes the wonder if I can get this phone to be a mini-agent.
Liquid has also been very good about keeping speed in mind, and the writeup here makes me expect similar. Really good stuff.
And to beat Qwen3.5-4B with such a capable model is amazing, on top of so many win/draws against 9b in the more general arena.
I can definitely see there being some roles for local agents that offload shell scripting & doing some scut work. I don't know what speed to expect but like, if someone has a decent NPU or GPU and can just get a bunch of basic systems work done with a small local model that could really speed up a lot of workflows that I see day after day after day.
Introducing LFM3: Every Modality for Specialized Intelligence
https://www.liquid.ai/blog/lfm3