Head to head · Open-weight models you run yourself · October 2026 research run
Kronos vs LFM3-Omni-2B
LFM3-Omni-2B scores 61 (C) on agent readiness against Kronos's 55.2 (C), and leads in 2 of 4 scored categories. Kronos leads on risk and documentation and upkeep. Both do open-weight models you run yourself.
Best open-weight models you download and run yourself for AI agents · All 4969 open weights comparisons
Which one, for what
Kronos C
Best for Agents that need a quick local forecast or synthetic sample of a candlestick series on modest hardware, for research or as one input among others.
Ahead on
- Risk, 50 against 40
- Documentation and upkeep, 61 against 49
Watch for
Runs only through the publisher's own PyTorch code from GitHub, in no named runtime and with no quantised build
Best for Voice and camera agents on a laptop or phone that want one small model for hearing, seeing, speaking and calling tools
Ahead on
- Reach, 80 against 55
- Agent interface, 70 against 60
Watch for
Only llama.cpp and Ollama run it in a release
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Reach LFM3-Omni-2B +25
Kronos 55
Memory 30, the publisher's Kronos-mini with its tokeniser is 0.03 GB and even Kronos-base is 0.43 GB in FP32. Runtimes 0, it runs only through the publisher's own PyTorch package from GitHub, and none of the six named runtimes supports it. Builds 0, FP32 safetensors only. Terms 15, MIT with nothing added. Download 10, nothing is gated. Hosted 0, no inference provider or publisher API serves it (provider mapping still empty on 4 November).
LFM3-Omni-2B 80
Memory 30, Liquid's Q4_K_M GGUF is 1.10 GB with its 0.29 GB projector file, and 1.39 GB × 1.2 = 1.7 GB, which fits 8 GB, well inside the 16 GB line. Runtimes 10, Released llama.cpp has the lfm3 architecture with the LFM3 vision and audio projectors and speech output (src/models/lfm3.cpp and tools/mtmd at b12242, with a realtime client example), and Ollama's library has an lfm3-omni entry. Builds 15, Liquid's GGUF repository holds Q4_0, Q4_K_M, Q8_0, F16 and BF16 files, and Liquid publishes 4-bit and 8-bit MLX builds and an ONNX repository, all in the LiquidAI organisation. Terms 10, the LFM Open License v1.0, a custom licence that lets anyone use it commercially for free below a threshold of $10M annual revenue. Download 10, the Hub API reports gated false for the model and its GGUF, MLX and ONNX repositories on 10 November 2026, so the files download with no account and nothing to accept. Hosted 5, Liquid's own API lists lfm3-omni-2b among its models, so the publisher hosts it. 30 + 10 + 15 + 10 + 10 + 5 = 80.
Documentation and upkeep Kronos +12
Kronos 61
Model card 11, intended use, architecture, parameters and context are there, limitations, languages and a cut-off aren't. Training data 20, the paper lists every exchange with asset and observation counts, the filtering and a June 2024 end. Last change 5, the reference code on 13 April 2026 (still the newest commit on 4 November, 205 days) and the Hub repositories on 9 September 2025. Responsiveness 20, the publisher answered 10 of 18 Hugging Face discussions (recounted by script on 4 November), though none since 24 November 2025, and the seven opened since April 2026 have no reply from it. Version policy 5, a first release. File health 0, the cards point to example data the repository has deleted and to licence and requirements links on a branch that doesn't exist.
LFM3-Omni-2B 49
Model card 14, Intended use (one on-device model in place of separate speech recognition, vision, language and speech models), architecture, parameters (2.17B), context (32K) and the text and speech languages. Training data 5, the card has no training section. Last change 20, the last commit, on 3 November 2026, changed the card's navigation icons, seven days before this check, and the one before it, on 28 October, documented video frame rate and frame limits. Responsiveness 0, none of the 12 discussions that aren't pull requests (27 October to 9 November 2026) has a reply from a LiquidAI member. Version policy 5, LFM3 came out in new repositories and the LFM2.5 models stay in theirs. File health 5, the card gives a 32K context while config.json gives the language model 128,000 positions and Liquid's API lists 128,000 for the hosted model, so the card and the files don't agree on context. 14 + 5 + 20 + 0 + 5 + 5 = 49.
Risk Kronos +10
Kronos 50
File safety 15, safetensors only, but the only documented loading path is the publisher's Python package in place of a runtime. Provenance 15, the files are in the NeoQuasar account the publisher's README links, with SHA-256 hashes. Safety evaluation 0, none published. Agent guidance 5, the README's general cautions that the fine-tuning pipeline isn't a production trading system. Licence risk 15, plain MIT; the broken licence link is charged to file health. Security programme 0, no reporting route found.
LFM3-Omni-2B 40
File safety 15, safetensors only, no .bin, .pt or .pth files (25). Provenance 15, files in the LiquidAI organisation, which Liquid's docs page for the model and its blog post link to (10). Safety evaluation 0, no safety results on the card or in Liquid's blog post for the LFM3 family, neither of which mentions safety testing. Agent guidance 0, Nothing on prompt injection, an instruction hierarchy, what refusals cover or safeguards to add. Licence risk 10, 15 less 5 for the $10M annual revenue threshold on commercial use. Security programme 0, no way to report a flaw found. 15 + 15 + 0 + 0 + 10 + 0 = 40.
Agent interface LFM3-Omni-2B +10
Kronos 60
Read for a forecasting model, the tool-calling, trained tool calling and structured-output lines stand for what it takes and returns. The card documents the DataFrame and timestamps it takes and the DataFrame it returns, and the publisher's KronosPredictor builds and parses them (25). It was trained on six K-line fields with calendar fields, one series per forecast (10). Output is a typed DataFrame indexed by the requested timestamps, the mean of the sampled paths (15). The input format is given only as code (10). Reasoning control and context score 0, with no reasoning and a 512-bar context (2,048 for Kronos-mini).
LFM3-Omni-2B 70
Chat template 20, chat_template.jinja in the repository (13,513 characters), with roles, images, video and audio, tools, deferred tools and tool results. Tool-calling format 25, the card and Liquid's tool-use page document tools passed through tools= in apply_chat_template, calls returned as XML and results sent back as tool messages. Trained tool calling 20, the template loops over every entry in an assistant turn's tool_calls, so several calls fit in one turn, and the card documents tool calling from spoken or written requests. Structured output 0, the card doesn't mention JSON or structured output for this model. Reasoning control 0, the card says this is a non-reasoning model and that enable_thinking=True is not supported, so there is no thinking to turn off or budget. Context 5, 32K tokens of input and output per the card. 20 + 25 + 20 + 0 + 0 + 5 = 70.
Score by category
| Category | Weight this run | Kronos | LFM3-Omni-2B | Edge |
|---|---|---|---|---|
| Capability | 35%pending | pending | pending | not scored in this run |
| Reach | 25%25 | 55 | 80 | LFM3-Omni-2B +25 |
| Risk | 20%20 | 50 | 40 | Kronos +10 |
| Agent interface | 10%10 | 60 | 70 | LFM3-Omni-2B +10 |
| Documentation and upkeep | 10%10 | 61 | 49 | Kronos +12 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 55.2/100 | C 61/100 |
Facts side by side
| Fact | Kronos | LFM3-Omni-2B |
|---|---|---|
| Kind | Open-weight model | Open-weight model |
| Vendor | Yu Shi (shiyu-coder, NeoQuasar), Tsinghua University | Liquid AI |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | ||
| Auth | None | None |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | MIT | LFM Open License v1.0 (free commercial use below $10M annual revenue) |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-04-13 | 2026-11-03 |
| Terms last updated | no document linked | no document linked |
| Privacy policy last updated | no document linked | no document linked |
| Popularity | 43k stars | none |
Verdicts
Kronos
Forecasts the next price bars from a history of up to 512 candlestick bars. Every size fits in under 0.5 GB and runs on a CPU, but only through the publisher's own Python package. Nobody has benchmarked it independently, its quickstart data was deleted from the repository, and the publisher hasn't replied since November 2025.
LFM3-Omni-2B
One 2.17B model that sees, listens and talks on an 8 GB machine and turns spoken requests into tool calls. Only llama.cpp and Ollama run it in a release. The context is 32K, it doesn't reason, Liquid hasn't answered a question on the repository, and there are no safety results or data sources.
Before you call either
Kronos
- Clone https://github.com/shiyu-coder/Kronos and
pip install -r requirements.txt, then loadKronos.from_pretrained("NeoQuasar/Kronos-small")andKronosTokenizer.from_pretrained("NeoQuasar/Kronos-Tokenizer-base")and wrap them in KronosPredictor - Pair Kronos-mini with Kronos-Tokenizer-2k and Kronos-small or Kronos-base with Kronos-Tokenizer-base, the cards' pairing
- The examples read examples/data/XSHG_5min_600977.csv, which no longer exists; point them at tests/data/regression_input.csv, 2,500 five-minute bars
- Keep the lookback at or under max_context, 512 bars, and pass the future timestamps you want as y_timestamp, since the calendar fields come from them
- Raise sample_count for a steadier forecast, but expect only the mean back; call the lower-level auto_regressive_inference yourself if you need the paths
- Treat forecasts as model output to check, not signals; the README says its own backtest pipeline isn't a production trading system
LFM3-Omni-2B
- Start it with
llama-server -hf LiquidAI/LFM3-Omni-2B-GGUF:Q4_K_M --jinjaorollama run lfm3-omni - Greedy decoding for text. For speech use audio_temperature 0.4 and audio_repetition_penalty 1.2, per the card
- The context is 32K, and llama.cpp samples video at 2 frames a second up to 384 frames
- Parse tool calls yourself from the XML it returns
- It doesn't reason, so don't pass enable_thinking
- Validate JSON output yourself
Questions
Which is better for AI agents, Kronos or LFM3-Omni-2B?
LFM3-Omni-2B scores 61 (C) on agent readiness against Kronos's 55.2 (C), and leads in 2 of 4 scored categories. Kronos leads on risk and documentation and upkeep.
Other comparisons with Kronos or LFM3-Omni-2B
- Agents-A1-4B vs Kronos
- Agents-A1-4B vs LFM3-Omni-2B
- Apertus v1.5 8B vs Kronos
- Apertus v1.5 8B vs LFM3-Omni-2B
- Apodex-1.1-mini vs Kronos
- Apodex-1.1-mini vs LFM3-Omni-2B
- Arete-27B vs Kronos
- Arete-27B vs LFM3-Omni-2B
- BigBang-v1 vs Kronos
- BigBang-v1 vs LFM3-Omni-2B
- Carbon-X vs Kronos
- Carbon-X vs LFM3-Omni-2B
- Cosmos-Reason2-2B vs Kronos
- Cosmos-Reason2-2B vs LFM3-Omni-2B
- Darwin-36B-Opus vs Kronos
- Darwin-36B-Opus vs LFM3-Omni-2B
- DeepSeek-V3.2 vs Kronos
- DeepSeek-V3.2 vs LFM3-Omni-2B
- DeepSeek V4.1 Flash vs Kronos
- DeepSeek V4.1 Flash vs LFM3-Omni-2B
- DeepSeek-V4-Flash-0731 vs Kronos
- DeepSeek-V4-Flash-0731 vs LFM3-Omni-2B
- DiffusionGemma 26B A4B IT vs Kronos
- DiffusionGemma 26B A4B IT vs LFM3-Omni-2B
- Gemma 4 12B IT vs Kronos
- Gemma 4 12B IT vs LFM3-Omni-2B
- Gemma 4 26B A4B IT vs Kronos
- Gemma 4 26B A4B IT vs LFM3-Omni-2B
- Gemma 4 31B IT vs Kronos
- Gemma 4 31B IT vs LFM3-Omni-2B
- Gemma 4 E2B IT vs Kronos
- Gemma 4 E2B IT vs LFM3-Omni-2B
- Gemma 4 E4B IT vs Kronos
- Gemma 4 E4B IT vs LFM3-Omni-2B
- GLM-4.5-Air vs Kronos
- GLM-4.5-Air vs LFM3-Omni-2B
- GLM-4.7-Flash vs Kronos
- GLM-4.7-Flash vs LFM3-Omni-2B
- GLM-5.3-Flash vs Kronos
- GLM-5.3-Flash vs LFM3-Omni-2B
- GLM-5.3 vs Kronos
- GLM-5.3 vs LFM3-Omni-2B
- gpt-oss-120b vs Kronos
- gpt-oss-120b vs LFM3-Omni-2B
- gpt-oss-20b vs Kronos
- gpt-oss-20b vs LFM3-Omni-2B
- Granite 4.2 30B vs Kronos
- Granite 4.2 30B vs LFM3-Omni-2B
- Granite 4.2 3B vs Kronos
- Granite 4.2 3B vs LFM3-Omni-2B
- Granite 4.2 8B vs Kronos
- Granite 4.2 8B vs LFM3-Omni-2B
- Hy-Memory-30B-A3B vs Kronos
- Hy-Memory-30B-A3B vs LFM3-Omni-2B
- Hy3 vs Kronos
- Hy3 vs LFM3-Omni-2B
- Inkling-Small vs Kronos
- Inkling-Small vs LFM3-Omni-2B
- Inkling vs Kronos
- Inkling vs LFM3-Omni-2B
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs Kronos
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs LFM3-Omni-2B
- Kimi K3.1 Pro vs Kronos
- Kimi K3.1 Pro vs LFM3-Omni-2B
- Kimi K3 vs Kronos
- Kimi K3 vs LFM3-Omni-2B
- Kolibri-1 vs Kronos
- Kolibri-1 vs LFM3-Omni-2B
- Kronos vs Laguna M.1
- Kronos vs Laguna S 2.1
- Kronos vs Laguna XS 2.1
- Kronos vs LBS-27B
- Kronos vs LFM2.5-2.6B
- Kronos vs LFM3-1.7B
- Kronos vs LFM3-Audio-2B
- Kronos vs LFM3-VL-2B
- Kronos vs Ling-3.0-tiny
- Kronos vs Ling-3.1-flash-1019
- Kronos vs MiMo-V2.6 Distill Qwen 9B
- Kronos vs MiniCPM-o 4.5
- Kronos vs MiniCPM-V 4.7 1B
- Kronos vs MiniCPM-V 4.7 35B-A3B
- Kronos vs MiniCPM5-2B
- Kronos vs MiniMax-M2.5
- Kronos vs MiniMax-M2.7
- Kronos vs MiniMax-M3.1-Flash
- Kronos vs Mistral Large 4
- Kronos vs Muse Glimmer 30B
- Kronos vs Nanbeige4.3-33B
- Kronos vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- Kronos vs Nemotron 3.5 Lightning 30B A3B
- Kronos vs Nemotron 3 Nano 30B A3B
- Kronos vs Nemotron 3 Nano 4B
- Kronos vs Nemotron 3 Nano Omni 30B A3B Reasoning
- Kronos vs Nemotron 3 Super 120B A12B
- Kronos vs Nemotron 3 Ultra 550B A55B
- Kronos vs occamy-1.0
- Kronos vs Olmo 3 7B Think
- Kronos vs Ornith-1.5-122B
- Kronos vs Ornith-1.5-35B-A3B
- Kronos vs Ornith-1.5-397B
- Kronos vs Ornith-1.5-9B
- Kronos vs Qwen-AgentWorld-35B-A3B
- Kronos vs Qwen3-30B-A3B-Instruct-2507
- Kronos vs Qwen3-4B-Instruct-2507
- Kronos vs Qwen3.5-0.8B
- Kronos vs Qwen3.5-122B-A10B
- Kronos vs Qwen3.5-2B
- Kronos vs Qwen3.5-397B-A17B
- Kronos vs Qwen3.5-4B
- Kronos vs Qwen3.5-9B
- Kronos vs Qwen3.6-27B
- Kronos vs Qwen3.6-35B-A3B
- Kronos vs Qwen3.8-27B
- Kronos vs Qwen3.8-Flash-Next
- Kronos vs Qwen3-Coder-30B-A3B-Instruct
- Kronos vs Qwen3-Coder-Next
- Kronos vs Qwen3-Omni-30B-A3B-Instruct
- Kronos vs Qwen3-VL-2B-Instruct
- Kronos vs Qwen3-VL-30B-A3B-Instruct
- Kronos vs Qwen3-VL-32B-Instruct
- Kronos vs Qwen3-VL-4B-Instruct
- Kronos vs Qwen3-VL-8B-Instruct
- Kronos vs Qwopus3.8-27B-Flash-V2
- Kronos vs Recursive Flint
- Kronos vs Ripple-65B Preview
- Kronos vs SmolLM3-3B
- Kronos vs Spark-X2.6-4B
- Kronos vs Swift 1.5 Qwen3.8-27B
- Kronos vs Swift 1.5 Qwen3.8-Flash-Next
- Kronos vs ThinkingCap (Qwen3.8 27B)
- Kronos vs Baidu Unlimited-OCR-2
- Laguna M.1 vs LFM3-Omni-2B
- Laguna S 2.1 vs LFM3-Omni-2B
- Laguna XS 2.1 vs LFM3-Omni-2B
- LBS-27B vs LFM3-Omni-2B
- LFM2.5-2.6B vs LFM3-Omni-2B
- LFM3-1.7B vs LFM3-Omni-2B
- LFM3-Audio-2B vs LFM3-Omni-2B
- LFM3-Omni-2B vs LFM3-VL-2B
- LFM3-Omni-2B vs Ling-3.0-tiny
- LFM3-Omni-2B vs Ling-3.1-flash-1019
- LFM3-Omni-2B vs MiMo-V2.6 Distill Qwen 9B
- LFM3-Omni-2B vs MiniCPM-o 4.5
- LFM3-Omni-2B vs MiniCPM-V 4.7 1B
- LFM3-Omni-2B vs MiniCPM-V 4.7 35B-A3B
- LFM3-Omni-2B vs MiniCPM5-2B
- LFM3-Omni-2B vs MiniMax-M2.5
- LFM3-Omni-2B vs MiniMax-M2.7
- LFM3-Omni-2B vs MiniMax-M3.1-Flash
- LFM3-Omni-2B vs Mistral Large 4
- LFM3-Omni-2B vs Muse Glimmer 30B
- LFM3-Omni-2B vs Nanbeige4.3-33B
- LFM3-Omni-2B vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- LFM3-Omni-2B vs Nemotron 3.5 Lightning 30B A3B
- LFM3-Omni-2B vs Nemotron 3 Nano 30B A3B
- LFM3-Omni-2B vs Nemotron 3 Nano 4B
- LFM3-Omni-2B vs Nemotron 3 Nano Omni 30B A3B Reasoning
- LFM3-Omni-2B vs Nemotron 3 Super 120B A12B
- LFM3-Omni-2B vs Nemotron 3 Ultra 550B A55B
- LFM3-Omni-2B vs occamy-1.0
- LFM3-Omni-2B vs Olmo 3 7B Think
- LFM3-Omni-2B vs Ornith-1.5-122B
- LFM3-Omni-2B vs Ornith-1.5-35B-A3B
- LFM3-Omni-2B vs Ornith-1.5-397B
- LFM3-Omni-2B vs Ornith-1.5-9B
- LFM3-Omni-2B vs Qwen-AgentWorld-35B-A3B
- LFM3-Omni-2B vs Qwen3-30B-A3B-Instruct-2507
- LFM3-Omni-2B vs Qwen3-4B-Instruct-2507
- LFM3-Omni-2B vs Qwen3.5-0.8B
- LFM3-Omni-2B vs Qwen3.5-122B-A10B
- LFM3-Omni-2B vs Qwen3.5-2B
- LFM3-Omni-2B vs Qwen3.5-397B-A17B
- LFM3-Omni-2B vs Qwen3.5-4B
- LFM3-Omni-2B vs Qwen3.5-9B
- LFM3-Omni-2B vs Qwen3.6-27B
- LFM3-Omni-2B vs Qwen3.6-35B-A3B
- LFM3-Omni-2B vs Qwen3.8-27B
- LFM3-Omni-2B vs Qwen3.8-Flash-Next
- LFM3-Omni-2B vs Qwen3-Coder-30B-A3B-Instruct
- LFM3-Omni-2B vs Qwen3-Coder-Next
- LFM3-Omni-2B vs Qwen3-Omni-30B-A3B-Instruct
- LFM3-Omni-2B vs Qwen3-VL-2B-Instruct
- LFM3-Omni-2B vs Qwen3-VL-30B-A3B-Instruct
- LFM3-Omni-2B vs Qwen3-VL-32B-Instruct
- LFM3-Omni-2B vs Qwen3-VL-4B-Instruct
- LFM3-Omni-2B vs Qwen3-VL-8B-Instruct
- LFM3-Omni-2B vs Qwopus3.8-27B-Flash-V2
- LFM3-Omni-2B vs Recursive Flint
- LFM3-Omni-2B vs Ripple-65B Preview
- LFM3-Omni-2B vs SmolLM3-3B
- LFM3-Omni-2B vs Spark-X2.6-4B
- LFM3-Omni-2B vs Swift 1.5 Qwen3.8-27B
- LFM3-Omni-2B vs Swift 1.5 Qwen3.8-Flash-Next
- LFM3-Omni-2B vs ThinkingCap (Qwen3.8 27B)
- LFM3-Omni-2B vs Baidu Unlimited-OCR-2
Machine-readable
- This page as Markdown
/compare/kronos-vs-lfm3-omni-2b.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/kronos.json·/api/v1/tools/lfm3-omni-2b.json - From a terminal
anchor compare kronos lfm3-omni-2b(the CLI) - Over MCP
compare_tools {"a": "kronos", "b": "lfm3-omni-2b"}at/mcp, no key