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

LBS-27B vs MiniMax-M2.5

MiniMax-M2.5 scores 57.5 (C) on agent readiness against LBS-27B's 53.9 (D), and leads in 2 of 4 scored categories. LBS-27B 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 3504 open weights comparisons

Which one, for what

LBS-27B D

Best for Agents with about 96 GB of GPU memory that need to find click targets on dense professional screenshots, or read fine detail in large images, and can run a small crop loop and wait for independent results.

Ahead on

  • Risk, 50 against 30
  • Documentation and upkeep, 43 against 22

Watch for

No independent benchmark result yet; ScreenSpot-Pro, OS-World-G, PerceptionBench and HR-Bench numbers are inclusionAI's own runs

MiniMax-M2.5 C

Best for Teams with a 4 to 8 GPU server who want an open agent and coding model with parallel tool calls and can live with its use policy

Ahead on

  • Reach, 65 against 55
  • Agent interface, 75 against 70

Watch for

230 GB in FP8, and about 155 GB for the smallest 4-bit library build, more than a 128 GB machine

Score by category

CategoryWeight this runLBS-27BMiniMax-M2.5Edge
Capability35%pendingpendingpendingnot scored in this run
Reach25%255565MiniMax-M2.5 +10
Risk20%205030LBS-27B +20
Agent interface10%107075MiniMax-M2.5 +5
Documentation and upkeep10%104322LBS-27B +21
Negative events≤1500
TotalD 53.9/100C 57.5/100

Facts side by side

FactLBS-27BMiniMax-M2.5
KindOpen-weight modelOpen-weight model
VendorinclusionAI (Ant Group)MiniMax
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0 (the card's metadata and licence section; the LICENSE file sits in the GitHub repository inclusionAI/UI-Venus on its LBS branch, not in the Hugging Face repository)MiniMax Model License (model) and modified MIT (code)
Read-only variant documentednono
llms.txtnono
Last release2026-10-262026-02-12
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 reviewsnone1.8/5 (4)

Verdicts

LBS-27B

A 27B Qwen3.8 fine-tune for GUI grounding that zooms into screenshots over a few turns before naming a point, and inclusionAI says it also helps with fine detail in large images. It needs about 96 GB at BF16 and a client that runs its crop actions. Every result so far is inclusionAI's own, with no safety results or injection guidance.

MiniMax-M2.5

MiniMax-M2.5 is a 230B mixture-of-experts model for coding and agent work, with parallel tool calls, a 196K context and parsers in vLLM and SGLang. It needs a 4-GPU server for FP8 or about 155 GB for a 4-bit build. The main risk is a licence replaced after release with a Prohibited Uses Policy while the card still says modified MIT.

Before you call either

LBS-27B

  1. Serve with vllm serve inclusionAI/LBS-27B --tensor-parallel-size 4 --max-model-len 65536, which is what the card's wrapper script runs; keep the context at 32,768 or more for multi-turn images
  2. Build the system prompt with build_system_prompt from the LBS branch's zoomin_grounding_protocol.py, send the screenshot after image_path: <name>, and don't pass tools; the model answers in plain text
  3. Parse <action>crop_image(image_path=..., x1=..., y1=..., x2=..., y2=...)</action>, cut the crop yourself and return it with its mapping to the original image; allow at most two crops per turn and three per episode
  4. Read the final answer as [x.xx,y.yy] on a 0 to 1000 scale of the original image, and use your own executor to click
  5. Pass reasoning_effort as xhigh, medium or low only, since the template raises an error for high, and don't count on thinking_budget, which the template ignores
  6. Don't turn on MTP speculative decoding; the MTP weights aren't in the repository though config.json names one MTP layer

MiniMax-M2.5

  1. Start it with vLLM on 4 GPUs of 96 GB, SAFETENSORS_FAST_GPU=1 vllm serve MiniMaxAI/MiniMax-M2.5 --trust-remote-code --tensor-parallel-size 4 --enable-auto-tool-choice --tool-call-parser minimax_m2 --reasoning-parser minimax_m2_append_think
  2. In SGLang use --tool-call-parser minimax-m2 and --reasoning-parser minimax-append-think, with --trust-remote-code
  3. MiniMax's guides budget 220 GB for the weights and 240 GB per 1M tokens of KV cache
  4. On a single large-memory machine, LM Studio's catalogue entry minimax/minimax-m2.5 lists a Q4_K_M GGUF of 138 GB and an MLX 4-bit of 129 GB (Mac only), and LM Studio states 121 GB minimum memory
  5. Sample with temperature 1.0, top_p 0.95 and top_k 40, as the card recommends
  6. Budget output tokens for thinking on every turn, since the template always opens a think block
  7. Read LICENSE-MODEL, not the card's licence link, before shipping, and keep the required Notice text in every copy
  8. Without the hardware, call it through Novita or Featherless AI; MiniMax's own API retires M2.5 on 18 November 2026

Questions

Which is better for AI agents, LBS-27B or MiniMax-M2.5?

MiniMax-M2.5 scores 57.5 (C) on agent readiness against LBS-27B's 53.9 (D), and leads in 2 of 4 scored categories. LBS-27B leads on risk and documentation and upkeep.

Other comparisons with LBS-27B or MiniMax-M2.5

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.