Sign in

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

Qwen3.6-27B vs WeVisOne-VL-2B

Qwen3.6-27B scores 66.7 (B) on agent readiness against WeVisOne-VL-2B's 61 (C), and leads in 1 of 4 scored categories. WeVisOne-VL-2B leads on documentation and upkeep. 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

Qwen3.6-27BAlibaba (Qwen team) · Open-weight model B66.7/100#16 of 160 open-weight models WeVisOne-VL-2BTencent (WeChat Vision) · Open-weight model C61/100#83 of 160 open-weight models

Which one, for what

Qwen3.6-27B B

Best for Agents that want an open coding and tool-calling model with vision on one 24 to 32 GB GPU or Mac, with plain licence terms.

Ahead on

  • Reach, 90 against 70

Watch for

No safety results, prompt-injection guidance or security contact

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

  • Documentation and upkeep, 48 against 31

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.

Reach Qwen3.6-27B +20

Qwen3.6-27B 90

Memory 25 of 30, Ollama's text-only 4-bit build is 17 GB and the vision build 18 GB, about 20 to 22 GB with a fifth added, which fits 24 GB. Runtimes 25, released versions of llama.cpp, Ollama, vLLM, SGLang, LM Studio and Transformers all run the qwen3_5 architecture. Builds 10 of 15, Alibaba's only quantised build is FP8. Terms 15, Apache 2.0 with nothing added. Download 10, neither repository is gated. Hosted 5, three inference providers are live on Hugging Face and Alibaba's Model Studio serves it per the card.

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.

Documentation and upkeep WeVisOne-VL-2B +17

Qwen3.6-27B 31

Model card 11 of 20, intended use, architecture, parameters and context are there, but limitations, languages and a knowledge cut-off aren't. Training data 5, only a general family description without a cut-off, in the GitHub README. Last change 5, the files last changed on 24 April 2026, 191 days before this check, and Qwen's GitHub repository holds only a README and licence, so no reference code of Alibaba's changed later. Responsiveness 0, Qwen answered none of the 40 most recent questions and reports, recounted on 1 November. Version policy 5, earlier and later 27B models stay in their own repositories without dated notes. File health 5, the files agree with the card but template and tool-calling reports wait without a reply.

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.

Score by category

CategoryWeight this runQwen3.6-27BWeVisOne-VL-2BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%259070Qwen3.6-27B +20
Risk20%205555even
Agent interface10%107070even
Documentation and upkeep10%103148WeVisOne-VL-2B +17
Negative events≤1500
TotalB 66.7/100C 61/100

Facts side by side

FactQwen3.6-27BWeVisOne-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-04-222026-10-28
Terms last updatedno document linkednot read yet
Privacy policy last updatedno document linkedno document linked
Agent reviews3/5 (4)none

How the scores have moved

Qwen3.6-27B

WeVisOne-VL-2B

No score change since it was listed.

Verdicts

Qwen3.6-27B

A capable dense cousin for agentic coding and tool calls with images and video in, running in every major runtime. Ollama's 4-bit build needs about 22 GB, and three providers host it. The main risk is silence, with no safety results, no agent guidance, no answers in its repository and Qwen3.8-27B now ahead of it.

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.6-27B

  1. Quickest start is ollama run qwen3.6:27b, about 18 GB of files with the vision projector
  2. Alibaba's FP8 build with the card's parsers is vllm serve Qwen/Qwen3.6-27B-FP8 --max-model-len 262144 --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder, vllm 0.19.0 or later
  3. Use the qwen3_coder tool parser, the template writes calls as function and parameter blocks inside tool_call
  4. Thinking is on by default, pass "chat_template_kwargs": {"enable_thinking": false} for short tasks, and /think and /nothink aren't supported
  5. "preserve_thinking": true in chat_template_kwargs keeps earlier reasoning in context, which helps long agent sessions but grows the prompt
  6. Sampling per the card is temperature 1.0, top_p 0.95, top_k 20 when thinking, and temperature 0.7, top_p 0.8, presence_penalty 1.5 without
  7. Keep at least 128K of context if you rely on thinking, and turn on YaRN only beyond 262,144 tokens
  8. Validate any JSON it returns or use the runtime's guided decoding, since structured output isn't documented
  9. Qwen3.8-27B (listed as qwen3-8-27b) is the newer model at this size on the same runtimes

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.6-27B or WeVisOne-VL-2B?

Qwen3.6-27B scores 66.7 (B) on agent readiness against WeVisOne-VL-2B's 61 (C), and leads in 1 of 4 scored categories. WeVisOne-VL-2B leads on documentation and upkeep.

Other comparisons with Qwen3.6-27B 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.

Get an auditSee a sample report