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

LBS-27B vs Nemotron 3.5 Lightning 30B A3B

Nemotron 3.5 Lightning 30B A3B scores 64.2 (B) on agent readiness against LBS-27B's 53.9 (D), and leads in every scored category. 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.5 Lightning 30B A3B B

Best for Agents on one 24 to 32 GB GPU or Mac that want a fast tool-calling reasoning model with long context and a permissive licence

Ahead on

  • Reach, 85 against 55
  • Risk, 75 against 50
  • Agent interface, 90 against 70
  • Documentation and upkeep, 70 against 43

Watch for

No safety evaluation results published

Score by category

CategoryWeight this runLBS-27BNemotron 3.5 Lightning 30B A3BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%255585Nemotron 3.5 Lightning 30B A3B +30
Risk20%205075Nemotron 3.5 Lightning 30B A3B +25
Agent interface10%107090Nemotron 3.5 Lightning 30B A3B +20
Documentation and upkeep10%104370Nemotron 3.5 Lightning 30B A3B +27
Negative events≤1500
TotalD 53.9/100B 64.2/100

Facts side by side

FactLBS-27BNemotron 3.5 Lightning 30B A3B
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)OpenMDW-1.1
Read-only variant documentednono
llms.txtnono
Last release2026-10-262026-08-11
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/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.5 Lightning 30B A3B

A small agent cousin, 3B active parameters, with trained parallel tool calls, a thinking switch and up to 1M tokens of context, under a permissive licence. It runs in about 23 GB from the GGUF or Ollama builds, and NVIDIA's NVFP4 build needs NVIDIA GPUs. The main risks are no published safety results and one answered question across two repositories.

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.5 Lightning 30B A3B

  1. Quickest start is ollama run nemotron-3.5-lightning, about 19 to 25 GB of files depending on the platform
  2. On the reference machine use llama-server -hf ggml-org/NVIDIA-Nemotron-3.5-Lightning-30B-A3B-GGUF:Q4_0 --jinja, since the card's Q4_K_M tag doesn't exist there and NVFP4 needs NVIDIA GPUs
  3. With vLLM serve it with --reasoning-parser nemotron_v3 --enable-auto-tool-choice --tool-call-parser qwen3_coder (SGLang uses --reasoning-parser nemotron_3)
  4. Use temperature=1.0 and top_p=0.95, as the card says
  5. Thinking is on by default. Pass chat_template_kwargs with enable_thinking false for short tasks
  6. For coding agents pass force_nonempty_content: true in chat_template_kwargs, which vLLM's nemotron_v3 parser reads so a cut-off reasoning trace still returns content
  7. Go past 262,144 tokens only with the card's flags (VLLM_ALLOW_LONG_MAX_MODEL_LEN=1, --max-model-len 1048576) and enough memory

Questions

Which is better for AI agents, LBS-27B or Nemotron 3.5 Lightning 30B A3B?

Nemotron 3.5 Lightning 30B A3B scores 64.2 (B) on agent readiness against LBS-27B's 53.9 (D), and leads in every scored category.

Other comparisons with LBS-27B or Nemotron 3.5 Lightning 30B A3B

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.