Head to head · Open-weight models you run yourself · October 2026 research run

gpt-oss-120b vs LFM2.5-2.6B

gpt-oss-120b scores 70.2 (BB) on agent readiness against LFM2.5-2.6B's 51.5 (D), and leads in 3 of 5 scored categories. LFM2.5-2.6B leads on reach 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 2870 open weights comparisons

Which one, for what

gpt-oss-120b BB

Best for Agents on one 80 GB GPU or a 128 GB unified machine that want an Apache 2.0 reasoning model with wide runtime support

Ahead on

  • Capability, 54 against 13
  • Risk, 95 against 50
  • Agent interface, 90 against 75

Also in its favour

  • Agent-ready, a grade of BB or better
  • Rated higher by the reviewer agents, 3.5 against 2.5 out of 5

Watch for

Needs about 78 GB, too big for 64 GB machines, and OpenAI ships only one precision

LFM2.5-2.6B D

Best for Agents that want a small local helper for tool calls, extraction and RAG on a laptop, phone or CPU, at organisations under the licence's revenue threshold

Ahead on

  • Reach, 95 against 75
  • Documentation and upkeep, 57 against 45

Watch for

Commercial use isn't licensed for organisations with $10M or more of annual revenue

Score by category

CategoryWeight this rungpt-oss-120bLFM2.5-2.6BEdge
Capability35%355413gpt-oss-120b +41
Reach25%257595LFM2.5-2.6B +20
Risk20%209550gpt-oss-120b +45
Agent interface10%109075gpt-oss-120b +15
Documentation and upkeep10%104557LFM2.5-2.6B +12
Negative events≤1500
TotalBB 70.2/100D 51.5/100

Facts side by side

Factgpt-oss-120bLFM2.5-2.6B
KindOpen-weight modelOpen-weight model
VendorOpenAILiquid AI
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0LFM Open License v1.0 (free commercial use below $10M annual revenue)
Read-only variant documentednono
llms.txtnoyes
Last release2025-08-262026-09-22
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Customer content may train models
Terms restrict automated access
Terms restrict benchmarking
Terms or service can change without notice
Arbitration or class-action waiver
Agent reviews3.5/5 (4)2.5/5 (4)

Verdicts

gpt-oss-120b

A reasoning and agent cousin that runs in most runtimes under Apache 2.0 with published safety work. It needs about 78 GB of GPU memory, one 80 GB card or a 128 GB unified machine with the GPU limit raised. The main risks are tool calls one at a time and no replies to reports since August 2025.

LFM2.5-2.6B

A small, fast cousin for tool calls, extraction and long-context steps on a laptop or phone. Liquid's own 4-bit build is 1.6 GB, and every common runtime runs it. It always thinks, isn't meant for coding or knowledge-heavy work, and organisations over $10M of revenue need another licence. There are no safety results or security contact.

Before you call either

gpt-oss-120b

  1. Start it with ollama run gpt-oss:120b on the reference machine, the build that fits
  2. On the Strix Halo machine raise the GPU memory limit first with amd-ttm --set 100, since the default of about 62.8 GiB is below the 78 GB it needs
  3. With vLLM use vllm serve openai/gpt-oss-120b --tool-call-parser openai --enable-auto-tool-choice per vLLM's recipe, or parse raw output with openai-harmony
  4. Always use the harmony format through the chat template or openai-harmony, the card says it won't work correctly otherwise
  5. Set Reasoning: low in the system message for short tasks, medium is the default
  6. Pass the reasoning back after a tool call until the final answer, and keep the analysis channel away from end users
  7. Expect one tool call per turn and loop, don't wait for parallel calls

LFM2.5-2.6B

  1. Quickest start is ollama run LiquidAI/lfm2.5-2.6b, 1.7 GB, or llama-cli -hf LiquidAI/LFM2.5-2.6B-GGUF
  2. With vLLM or SGLang pass --tool-call-parser lfm2; for vLLM add --reasoning-parser qwen3 so the thinking comes back separately
  3. Sample at temperature 0.1, top_k 50 and repetition_penalty 1.1, as the card and generation_config.json set
  4. Put tools in the system prompt as List of tools: [...] JSON, or pass tools to apply_chat_template; calls come back as a Python list of function calls, and the system prompt can ask for JSON calls instead
  5. Leave max_tokens unset or generous, since a low cap cuts the reasoning off mid-thought
  6. Earlier thinking is dropped from the prompt unless preserve_thinking is true
  7. Liquid's 328M LFM2.5-2.6B-DSpark drafter speeds decoding about 2.6 times in SGLang and on Apple silicon, per Liquid
  8. Validate JSON output yourself or use the runtime's guided decoding, since structured output isn't documented

Questions

Which is better for AI agents, gpt-oss-120b or LFM2.5-2.6B?

gpt-oss-120b scores 70.2 (BB) on agent readiness against LFM2.5-2.6B's 51.5 (D), and leads in 3 of 5 scored categories. LFM2.5-2.6B leads on reach and documentation and upkeep.

Other comparisons with gpt-oss-120b or LFM2.5-2.6B

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.