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

LBS-27B vs Nemotron 3 Nano 4B

Nemotron 3 Nano 4B scores 56.8 (C) on agent readiness against LBS-27B's 53.9 (D), and leads in 3 of 4 scored categories. 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.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

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

Nemotron 3 Nano 4B C

Best for Agents on laptops, edge boards and small GPUs that need a cheap local tool-calling helper in English

Ahead on

  • Reach, 90 against 55
  • Risk, 65 against 50
  • Documentation and upkeep, 55 against 43

Watch for

The card's Transformers and vLLM commands pass trust_remote_code and load a parser plugin from the repository

Score by category

CategoryWeight this runLBS-27BNemotron 3 Nano 4BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%255590Nemotron 3 Nano 4B +35
Risk20%205065Nemotron 3 Nano 4B +15
Agent interface10%107070even
Documentation and upkeep10%104355Nemotron 3 Nano 4B +12
Negative events≤1500
TotalD 53.9/100C 56.8/100

Facts side by side

FactLBS-27BNemotron 3 Nano 4B
KindOpen-weight modelOpen-weight model
VendorinclusionAI (Ant Group)NVIDIA
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)NVIDIA Nemotron Open Model License
Read-only variant documentednono
llms.txtnono
Last release2026-10-262026-03-16
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 reviewsnone3.3/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.

Nemotron 3 Nano 4B

A tiny reasoning cousin with trained tool calls, a thinking switch and 262,144 tokens of context, running in about 4 GB from NVIDIA's own GGUF on almost any machine. The main risks are serving commands that run repository code, no published safety results, a tool format left to the template, and files untouched and questions unanswered since March.

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

Nemotron 3 Nano 4B

  1. Quickest start is ollama run nemotron-3-nano:4b, a 2.8 GB build
  2. With llama.cpp use llama-server -hf nvidia/NVIDIA-Nemotron-3-Nano-4B-GGUF --jinja, NVIDIA's own Q4_K_M file
  3. With vLLM, download nano_v3_reasoning_parser.py from the repository first and serve with --enable-auto-tool-choice --tool-call-parser qwen3_coder --reasoning-parser-plugin nano_v3_reasoning_parser.py --reasoning-parser nano_v3
  4. The card's Transformers snippet names nvidia/NVIDIA-Nemotron-3-Nano-4B, use nvidia/NVIDIA-Nemotron-3-Nano-4B-BF16 instead
  5. Thinking is on by default. Pass enable_thinking=False to the chat template for short tasks
  6. Use temperature 1.0 and top_p 0.95 for reasoning and temperature 0.6 with top_p 0.95 for tool calling, as the card says
  7. It's tuned for English only, and validate JSON yourself, since structured output isn't documented

Questions

Which is better for AI agents, LBS-27B or Nemotron 3 Nano 4B?

Nemotron 3 Nano 4B scores 56.8 (C) on agent readiness against LBS-27B's 53.9 (D), and leads in 3 of 4 scored categories.

Other comparisons with LBS-27B or Nemotron 3 Nano 4B

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.