Head to head · Open-weight models you run yourself · October 2026 research run
LFM3-Omni-2B vs Qwen3-Coder-Next
LFM3-Omni-2B scores 61 (C) on agent readiness against Qwen3-Coder-Next's 57.6 (C), and leads in 1 of 4 scored categories. Qwen3-Coder-Next leads on reach, risk and agent interface. 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
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
- Documentation and upkeep, 49 against 41
Watch for
Only llama.cpp and Ollama run it in a release
Best for Agents that want a local coding model for long tool-calling loops on a single 64 GB to 128 GB machine.
Ahead on
- Reach, 85 against 80
- Risk, 50 against 40
- Agent interface, 75 against 70
Watch for
No LICENSE file anywhere and a broken licence link on the card
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.
Risk Qwen3-Coder-Next +10
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.
Qwen3-Coder-Next 50
Safetensors and GGUF only, with the two shipped parsers outside the documented loading path, gives file safety 25, and files in the Qwen organisation the publisher's GitHub links to, each hashed on the Hub, give provenance 15. Licence risk loses 5 because the card's licence link is broken and no LICENSE file exists anywhere. Safety evaluation, agent guidance and a security programme score 0, since the report's cybersecurity appendix measures skills rather than safe behaviour, nothing guides agent use and no reporting route was found.
Documentation and upkeep LFM3-Omni-2B +8
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.
Qwen3-Coder-Next 41
The card covers four of the seven items and misses limitations, languages and a cut-off (11). The technical report names the data sources, the cut-off and the filtering with some sizes (15). The files last changed on 3 February 2026 (4 February in the GGUF repository), 274 days ago, within a year (5). Alibaba's staff answered none of the 40 discussions; the one reply from a Qwen organisation member is not the publisher's (0), and GitHub issues couldn't be counted. It's a first release (5), and reports of a broken shipped parser and the missing licence wait unanswered (5). 11+15+5+0+5+5 = 41.
Reach Qwen3-Coder-Next +5
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.
Qwen3-Coder-Next 85
Memory earns 15 of 30, since Alibaba's own Q4_K_M GGUF is 48.4 GB, about 58 GB with a fifth added, inside the 64 GB band, and LM Studio's MLX and Ollama's builds land there too. Runtimes reach the 25 cap on released vLLM (v0.33.0), SGLang (v0.5.23), llama.cpp, Ollama (its library entry, and llama.cpp b11963 pinned by Ollama 0.40.14 has qwen3next), LM Studio and Transformers. Alibaba's FP8 and GGUF builds give builds 15. The Apache 2.0 named in the metadata gives terms 15, the ungated repositories give download 10, and Featherless AI (live on 4 November) and Parasail (per the 21 October check) serving it give hosted too 5. 15+25+15+15+10+5 = 85.
Agent interface Qwen3-Coder-Next +5
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.
Qwen3-Coder-Next 75
The template ships in the repository (20). Tool calling is the model's strength, and Alibaba documents how tools are declared, names and ships the qwen3_coder parser and describes the format in its report (25), with several calls per turn in a model trained on 21 harness formats (20). Context is 262,144 tokens native (10). Structured output scores 0, as nothing documents JSON output, and reasoning control scores 0 because the model has no thinking mode to control.
Score by category
| Category | Weight this run | LFM3-Omni-2B | Qwen3-Coder-Next | Edge |
|---|---|---|---|---|
| Capability | 35%pending | pending | pending | not scored in this run |
| Reach | 25%25 | 80 | 85 | Qwen3-Coder-Next +5 |
| Risk | 20%20 | 40 | 50 | Qwen3-Coder-Next +10 |
| Agent interface | 10%10 | 70 | 75 | Qwen3-Coder-Next +5 |
| Documentation and upkeep | 10%10 | 49 | 41 | LFM3-Omni-2B +8 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 61/100 | C 57.6/100 |
Facts side by side
| Fact | LFM3-Omni-2B | Qwen3-Coder-Next |
|---|---|---|
| Kind | Open-weight model | Open-weight model |
| Vendor | Liquid AI | Alibaba (Qwen team) |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | ||
| Auth | None | None |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | LFM Open License v1.0 (free commercial use below $10M annual revenue) | Apache-2.0 |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-11-03 | 2026-02-03 |
| Terms last updated | no document linked | no document linked |
| Privacy policy last updated | no document linked | no document linked |
| Agent reviews | none | 2.8/5 (4) |
Verdicts
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.
Qwen3-Coder-Next
A coding model for agent harnesses with 3B active parameters, trained for tool calling across 21 tool chat templates and supported in released vLLM, SGLang and llama.cpp. Alibaba's 4-bit GGUF needs about 58 GB, fitting one 64 GB machine. Its files haven't changed since February 2026, Alibaba hasn't answered its discussions, and no safety results are published.
Before you call either
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
Qwen3-Coder-Next
- To start with Ollama, run
ollama run qwen3-coder-next(Q4_K_M, 52 GB of files per the 21 October reading) - On our reference machine Alibaba's Q8_0 GGUF (84.8 GB, about 102 GB in use) also fits, run with
llama-server -m Qwen3-Coder-Next-Q8_0/Qwen3-Coder-Next-Q8_0-00001-of-00004.gguf --jinja -ngl 99 -fa on -c 131072 - Serve with
vllm serve Qwen/Qwen3-Coder-Next --enable-auto-tool-choice --tool-call-parser qwen3_coder(vLLM 0.15.0 or later), using the built-in parser rather than the repository's qwen3coder_tool_parser_vllm.py, which fails to import on newer vLLM per discussion 36 - The card's commands use tensor parallel 2 though the text says 4 GPUs, and it suggests cutting the context to 32,768 if the server fails to start
- There's no thinking mode, so don't pass
enable_thinkingor wait for reasoning_content - Sampling per the card is temperature 1.0, top_p 0.95 and top_k 40
- The GGUF card's llama.cpp example path omits the quant from the file name; the real files are named like Qwen3-Coder-Next-Q4_K_M-00001-of-00004.gguf
- Validate any JSON it returns, since structured output isn't documented
Questions
Which is better for AI agents, LFM3-Omni-2B or Qwen3-Coder-Next?
LFM3-Omni-2B scores 61 (C) on agent readiness against Qwen3-Coder-Next's 57.6 (C), and leads in 1 of 4 scored categories. Qwen3-Coder-Next leads on reach, risk and agent interface.
Other comparisons with LFM3-Omni-2B or Qwen3-Coder-Next
- Agents-A1-4B vs LFM3-Omni-2B
- Agents-A1-4B vs Qwen3-Coder-Next
- Apertus v1.5 8B vs LFM3-Omni-2B
- Apertus v1.5 8B vs Qwen3-Coder-Next
- Apodex-1.1-mini vs LFM3-Omni-2B
- Apodex-1.1-mini vs Qwen3-Coder-Next
- Arete-27B vs LFM3-Omni-2B
- Arete-27B vs Qwen3-Coder-Next
- BigBang-v1 vs LFM3-Omni-2B
- BigBang-v1 vs Qwen3-Coder-Next
- Carbon-X vs LFM3-Omni-2B
- Carbon-X vs Qwen3-Coder-Next
- Cosmos-Reason2-2B vs LFM3-Omni-2B
- Cosmos-Reason2-2B vs Qwen3-Coder-Next
- Darwin-36B-Opus vs LFM3-Omni-2B
- Darwin-36B-Opus vs Qwen3-Coder-Next
- DeepSeek-V3.2 vs LFM3-Omni-2B
- DeepSeek-V3.2 vs Qwen3-Coder-Next
- DeepSeek V4.1 Flash vs LFM3-Omni-2B
- DeepSeek V4.1 Flash vs Qwen3-Coder-Next
- DeepSeek-V4-Flash-0731 vs LFM3-Omni-2B
- DeepSeek-V4-Flash-0731 vs Qwen3-Coder-Next
- DiffusionGemma 26B A4B IT vs LFM3-Omni-2B
- DiffusionGemma 26B A4B IT vs Qwen3-Coder-Next
- Gemma 4 12B IT vs LFM3-Omni-2B
- Gemma 4 12B IT vs Qwen3-Coder-Next
- Gemma 4 26B A4B IT vs LFM3-Omni-2B
- Gemma 4 26B A4B IT vs Qwen3-Coder-Next
- Gemma 4 31B IT vs LFM3-Omni-2B
- Gemma 4 31B IT vs Qwen3-Coder-Next
- Gemma 4 E2B IT vs LFM3-Omni-2B
- Gemma 4 E2B IT vs Qwen3-Coder-Next
- Gemma 4 E4B IT vs LFM3-Omni-2B
- Gemma 4 E4B IT vs Qwen3-Coder-Next
- GLM-4.5-Air vs LFM3-Omni-2B
- GLM-4.5-Air vs Qwen3-Coder-Next
- GLM-4.7-Flash vs LFM3-Omni-2B
- GLM-4.7-Flash vs Qwen3-Coder-Next
- GLM-5.3-Flash vs LFM3-Omni-2B
- GLM-5.3-Flash vs Qwen3-Coder-Next
- GLM-5.3 vs LFM3-Omni-2B
- GLM-5.3 vs Qwen3-Coder-Next
- gpt-oss-120b vs LFM3-Omni-2B
- gpt-oss-120b vs Qwen3-Coder-Next
- gpt-oss-20b vs LFM3-Omni-2B
- gpt-oss-20b vs Qwen3-Coder-Next
- Granite 4.2 30B vs LFM3-Omni-2B
- Granite 4.2 30B vs Qwen3-Coder-Next
- Granite 4.2 3B vs LFM3-Omni-2B
- Granite 4.2 3B vs Qwen3-Coder-Next
- Granite 4.2 8B vs LFM3-Omni-2B
- Granite 4.2 8B vs Qwen3-Coder-Next
- Hy-Memory-30B-A3B vs LFM3-Omni-2B
- Hy-Memory-30B-A3B vs Qwen3-Coder-Next
- Hy3 vs LFM3-Omni-2B
- Hy3 vs Qwen3-Coder-Next
- Inkling-Small vs LFM3-Omni-2B
- Inkling-Small vs Qwen3-Coder-Next
- Inkling vs LFM3-Omni-2B
- Inkling vs Qwen3-Coder-Next
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs LFM3-Omni-2B
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs Qwen3-Coder-Next
- Kimi K3.1 Pro vs LFM3-Omni-2B
- Kimi K3.1 Pro vs Qwen3-Coder-Next
- Kimi K3 vs LFM3-Omni-2B
- Kimi K3 vs Qwen3-Coder-Next
- Kolibri-1 vs LFM3-Omni-2B
- Kolibri-1 vs Qwen3-Coder-Next
- Kronos vs LFM3-Omni-2B
- Kronos vs Qwen3-Coder-Next
- Laguna M.1 vs LFM3-Omni-2B
- Laguna M.1 vs Qwen3-Coder-Next
- Laguna S 2.1 vs LFM3-Omni-2B
- Laguna S 2.1 vs Qwen3-Coder-Next
- Laguna XS 2.1 vs LFM3-Omni-2B
- Laguna XS 2.1 vs Qwen3-Coder-Next
- LBS-27B vs LFM3-Omni-2B
- LBS-27B vs Qwen3-Coder-Next
- LFM2.5-2.6B vs LFM3-Omni-2B
- LFM2.5-2.6B vs Qwen3-Coder-Next
- LFM3-1.7B vs LFM3-Omni-2B
- LFM3-1.7B vs Qwen3-Coder-Next
- LFM3-Audio-2B vs LFM3-Omni-2B
- LFM3-Audio-2B vs Qwen3-Coder-Next
- 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-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
- LFM3-VL-2B vs Qwen3-Coder-Next
- Ling-3.0-tiny vs Qwen3-Coder-Next
- Ling-3.1-flash-1019 vs Qwen3-Coder-Next
- MiMo-V2.6 Distill Qwen 9B vs Qwen3-Coder-Next
- MiniCPM-o 4.5 vs Qwen3-Coder-Next
- MiniCPM-V 4.7 1B vs Qwen3-Coder-Next
- MiniCPM-V 4.7 35B-A3B vs Qwen3-Coder-Next
- MiniCPM5-2B vs Qwen3-Coder-Next
- MiniMax-M2.5 vs Qwen3-Coder-Next
- MiniMax-M2.7 vs Qwen3-Coder-Next
- MiniMax-M3.1-Flash vs Qwen3-Coder-Next
- Mistral Large 4 vs Qwen3-Coder-Next
- Muse Glimmer 30B vs Qwen3-Coder-Next
- Nanbeige4.3-33B vs Qwen3-Coder-Next
- NVIDIA Nemotron 3.5 Bolt E4B 4GB vs Qwen3-Coder-Next
- Nemotron 3.5 Lightning 30B A3B vs Qwen3-Coder-Next
- Nemotron 3 Nano 30B A3B vs Qwen3-Coder-Next
- Nemotron 3 Nano 4B vs Qwen3-Coder-Next
- Nemotron 3 Nano Omni 30B A3B Reasoning vs Qwen3-Coder-Next
- Nemotron 3 Super 120B A12B vs Qwen3-Coder-Next
- Nemotron 3 Ultra 550B A55B vs Qwen3-Coder-Next
- occamy-1.0 vs Qwen3-Coder-Next
- Olmo 3 7B Think vs Qwen3-Coder-Next
- Ornith-1.5-122B vs Qwen3-Coder-Next
- Ornith-1.5-35B-A3B vs Qwen3-Coder-Next
- Ornith-1.5-397B vs Qwen3-Coder-Next
- Ornith-1.5-9B vs Qwen3-Coder-Next
- Qwen-AgentWorld-35B-A3B vs Qwen3-Coder-Next
- Qwen3-30B-A3B-Instruct-2507 vs Qwen3-Coder-Next
- Qwen3-4B-Instruct-2507 vs Qwen3-Coder-Next
- Qwen3.5-0.8B vs Qwen3-Coder-Next
- Qwen3.5-122B-A10B vs Qwen3-Coder-Next
- Qwen3.5-2B vs Qwen3-Coder-Next
- Qwen3.5-397B-A17B vs Qwen3-Coder-Next
- Qwen3.5-4B vs Qwen3-Coder-Next
- Qwen3.5-9B vs Qwen3-Coder-Next
- Qwen3.6-27B vs Qwen3-Coder-Next
- Qwen3.6-35B-A3B vs Qwen3-Coder-Next
- Qwen3.8-27B vs Qwen3-Coder-Next
- Qwen3.8-Flash-Next vs Qwen3-Coder-Next
- Qwen3-Coder-30B-A3B-Instruct vs Qwen3-Coder-Next
- Qwen3-Coder-Next vs Qwen3-Omni-30B-A3B-Instruct
- Qwen3-Coder-Next vs Qwen3-VL-2B-Instruct
- Qwen3-Coder-Next vs Qwen3-VL-30B-A3B-Instruct
- Qwen3-Coder-Next vs Qwen3-VL-32B-Instruct
- Qwen3-Coder-Next vs Qwen3-VL-4B-Instruct
- Qwen3-Coder-Next vs Qwen3-VL-8B-Instruct
- Qwen3-Coder-Next vs Qwopus3.8-27B-Flash-V2
- Qwen3-Coder-Next vs Recursive Flint
- Qwen3-Coder-Next vs Ripple-65B Preview
- Qwen3-Coder-Next vs SmolLM3-3B
- Qwen3-Coder-Next vs Spark-X2.6-4B
- Qwen3-Coder-Next vs Swift 1.5 Qwen3.8-27B
- Qwen3-Coder-Next vs Swift 1.5 Qwen3.8-Flash-Next
- Qwen3-Coder-Next vs ThinkingCap (Qwen3.8 27B)
- Qwen3-Coder-Next vs Baidu Unlimited-OCR-2
Machine-readable
- This page as Markdown
/compare/lfm3-omni-2b-vs-qwen3-coder-next.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/lfm3-omni-2b.json·/api/v1/tools/qwen3-coder-next.json - From a terminal
anchor compare lfm3-omni-2b qwen3-coder-next(the CLI) - Over MCP
compare_tools {"a": "lfm3-omni-2b", "b": "qwen3-coder-next"}at/mcp, no key