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

Qwen3.5-0.8B vs WeVisOne-VL-2B

WeVisOne-VL-2B scores 61 (C) on agent readiness against Qwen3.5-0.8B's 46.7 (D), and leads in 2 of 4 scored categories. Qwen3.5-0.8B leads on reach. Both do open-weight models you run yourself.

Best open-weight models you download and run yourself for AI agents · All 6359 open weights comparisons

Which one, for what

Qwen3.5-0.8B D

Best for Builders who want a near-free local helper or fine-tuning base for narrow tasks on a phone-class device, laptop or CPU

Ahead on

  • Reach, 80 against 70

Watch for

No quantised build from Alibaba and no inference provider found

WeVisOne-VL-2B C

Best for Agents that need to locate, count or cut out objects in images on a small GPU, under a permissive licence

Ahead on

  • Agent interface, 70 against 60
  • Documentation and upkeep, 48 against 37

Watch for

The pixel decoder ships as a pickle file

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.

Documentation and upkeep WeVisOne-VL-2B +11

Qwen3.5-0.8B 37

The card covers six of the seven items, missing only a cut-off (17), because it states the intended uses and warns about thinking loops. Training data is a general description without a cut-off (5). The files last changed on 2 March 2026, 248 days before this check, within a year (5). No Qwen member has answered any of the 15 discussions that aren't pull requests (0). Qwen3-0.6B stays in its own repository without a dated note (5), and a template fix and the missing generation_config.json wait unanswered (5). 17+5+5+0+5+5 = 37.

WeVisOne-VL-2B 48

Model card 8, Intended use, limitations and the architecture are on the card. Training data 5, A general description in the README of a data engine and over 100 million annotated images, with no sources named and no cut-off. Last change 20, the last commit, on 28 October 2026, put the weights back in BF16, 13 days before this check. Responsiveness 0, the one discussion that isn't a pull request (23 October 2026) has no reply from a tencent member, counted on 10 November by author flags and dates with a script, text not read. Version policy 5, A first release. File health 10, Config, template and card agree on the Qwen3-VL classes, and the card names mask_decoder.pt as required and it's there. 8 + 5 + 20 + 0 + 5 + 10 = 48.

Reach Qwen3.5-0.8B +10

Qwen3.5-0.8B 80

Memory earns the full 30, since LM Studio's Q4_K_M build with its projector is 0.73 GB (0.88 GB with the fifth added) and Ollama's Q8_0 build was 1.0 GB, both far within 16 GB. Alibaba publishes no quantised 0.8B, so builds scores 0. Runtimes reach the 25 cap on llama.cpp, Ollama (through its pinned llama.cpp), vLLM, SGLang, LM Studio and Transformers. Apache 2.0 with nothing added gives terms 15 and the ungated repository download 10. Hosted too scores 0, as the Hub maps no inference provider to this size. 30+25+0+15+10+0 = 80.

WeVisOne-VL-2B 70

Memory 30, the only build from Tencent is the BF16 safetensors file with its decoder, 4.92 GB, and 4.92 GB × 1.2 = 5.9 GB, within 16 GB. No runtime library has a build. Runtimes 15, the architecture is Qwen3VLForConditionalGeneration, which vLLM 0.33.0, SGLang 0.5.23 and Transformers 5.22.2 run from the safetensors file, three at 5 each. Builds 0, Tencent publishes the BF16 weights only. Terms 15, Apache 2.0 in the card's metadata with the LICENSE file in the repository, and nothing added. Download 10, the Hub API reports gated false on 10 November 2026, so the files download with no account and nothing to accept. Hosted 0, Hugging Face maps no inference provider to it. 30 + 15 + 0 + 15 + 10 + 0 = 70.

Agent interface WeVisOne-VL-2B +10

Qwen3.5-0.8B 60

The template ships in the repository (20) and the model was trained for tool use with several calls per turn in the template (20). Tool-calling format gets 10, because the card names the qwen3_coder parser but leaves the format to the template. Reasoning control scores 0, since the card shows how to turn thinking on but not where the reasoning comes back. 262,144 tokens is native (10). Structured output scores 0, as nothing documents JSON output for the model. 20+10+20+0+0+10 = 60.

WeVisOne-VL-2B 70

Chat template 20, chat_template.jinja in the repository (5,292 characters), Qwen3-VL's template. Tool-calling format 25, Read for a perception model as what it takes and returns. Trained tool calling 10, Read for a perception model as the inputs it was trained to use. Structured output 15, Read for a perception model as typed outputs. Reasoning control 0, the card says it writes structured output directly with no chain-of-thought reasoning. Context 0, Tencent states no context length for it. 20 + 25 + 10 + 15 + 0 + 0 = 70.

Score by category

CategoryWeight this runQwen3.5-0.8BWeVisOne-VL-2BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%258070Qwen3.5-0.8B +10
Risk20%205555even
Agent interface10%106070WeVisOne-VL-2B +10
Documentation and upkeep10%103748WeVisOne-VL-2B +11
Negative events≤1500
TotalD 46.7/100C 61/100

Facts side by side

FactQwen3.5-0.8BWeVisOne-VL-2B
KindOpen-weight modelOpen-weight model
VendorAlibaba (Qwen team)Tencent (WeChat Vision)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-03-022026-10-28
Terms last updatedno document linkednot read yet
Privacy policy last updatedno document linkedno document linked
Agent reviews2.8/5 (4)none

Verdicts

Qwen3.5-0.8B

A tiny vision-language model for prototypes, fine-tuning and narrow local steps such as routing, tagging or reading an image. It runs in about 1 GB at 4 or 8 bits in six runtimes under plain Apache 2.0. Keep thinking off, since the card warns it loops. The card has no safety results, and Qwen has answered none of its discussions.

WeVisOne-VL-2B

A small Apache 2.0 perception model that finds, counts, reads and cuts out what you name in an image, and says None when it isn't there. Boxes and points run in vLLM, SGLang or Transformers. Masks and mattes need Tencent's package and a pickle file. Two weeks old, with no questions answered yet and no safety results.

Before you call either

Qwen3.5-0.8B

  1. Smallest start is ollama run qwen3.5:0.8b, or qwen3.5:0.8b-q8_0 at 1.0 GB
  2. Full precision vllm serve Qwen/Qwen3.5-0.8B --port 8000 --max-model-len 262144 --enable-auto-tool-choice --tool-call-parser qwen3_coder
  3. Thinking is off by default; if you turn it on with "chat_template_kwargs": {"enable_thinking": true}, stream and cut off runaway output, since the card warns of thinking loops, and add --reasoning-parser qwen3 in vLLM or SGLang to split the reasoning out
  4. There's no generation_config.json, so pass the card's sampling yourself, for example temperature=1.0, top_p=1.0, top_k=20, presence_penalty=2.0 for text without thinking
  5. Use it for narrow steps or as a fine-tuning base, not as the main agent, as the card itself suggests
  6. Validate any JSON it returns, since structured output isn't documented

WeVisOne-VL-2B

  1. Use Tencent's package: WeVisOneVL("tencent/WeVisOne-VL-2B", backend="vllm") then model.predict(image, task=..., query=...)
  2. Tasks are detection, referring, point, count_box, count_point, ocr, ocr_grounding, segmentation and matting
  3. A None answer means the target isn't in the image. Treat it as a result, not an error
  4. mask_decoder.pt is a pickle. Load it only from the tencent repository, and check its SHA-256 against the Hub's
  5. Send one image a turn. Video grids are rejected by the decoder
  6. The card says it isn't for identifying individuals or for high-impact decisions on its own

Questions

Which is better for AI agents, Qwen3.5-0.8B or WeVisOne-VL-2B?

WeVisOne-VL-2B scores 61 (C) on agent readiness against Qwen3.5-0.8B's 46.7 (D), and leads in 2 of 4 scored categories. Qwen3.5-0.8B leads on reach.

Other comparisons with Qwen3.5-0.8B or WeVisOne-VL-2B

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.