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

Qwen3.8-Flash-Next vs WeVisOne-VL-4B

Qwen3.8-Flash-Next and WeVisOne-VL-4B score within a point of each other on agent readiness, 61.8 (C) and 61 (C). WeVisOne-VL-4B leads on reach, 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 6359 open weights comparisons

Which one, for what

Qwen3.8-Flash-Next C

Best for Teams with a multi-GPU server or a 128 GB Mac who want Qwen's newest sparse architecture for agentic coding and multimodal work, and aren't a hosted-model or coding-assistant business.

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

Watch for

No build fits the reference machine's 107.4 GB, and Ollama's smallest Linux build is 120 GB

WeVisOne-VL-4B 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

  • Reach, 70 against 65
  • Risk, 55 against 45
  • Documentation and upkeep, 48 against 36

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-4B +12

Qwen3.8-Flash-Next 36

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 0, not described beyond a token count relative to an earlier model. Last change 15, the FP8 config fix on 31 August 2026, 63 days before 2 November. Responsiveness 0, Qwen answered none of the 40 most recent questions and reports (29 to 79, 27 August to 26 October), its only reply came in the first week. Version policy 5, a first release with nothing replaced. File health 5, the files agree with the card, but a 19 October report about the template and a pull request to fix it still wait without a reply. 11 + 0 + 15 + 0 + 5 + 5 = 36.

WeVisOne-VL-4B 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 27 October 2026, added links to the paper and project page, 14 days before this check. Responsiveness 0, Neither of the 2 discussions that aren't pull requests (23 and 26 October 2026) has a 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, 14 days old. 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.

Risk WeVisOne-VL-4B +10

Qwen3.8-Flash-Next 45

File safety 25, safetensors only and nothing from the repository runs to load it or build prompts. Provenance 15, the files are in the Qwen organisation that Qwen's GitHub links to, and every file has a checksum. Safety evaluation 0, none published on the card or in the technical report. Agent guidance 0, nothing on prompt injection, refusals or safeguards. Licence risk 5 of 15, 5 off for the field-of-use limit on model-as-a-service and coding or office assistant businesses and 5 off for the naming duty above a user or revenue threshold. Security programme 0, no security.txt, disclosure policy or security contact for Qwen was found, and Alibaba's group security centre couldn't be checked, so it's scored as absent.

WeVisOne-VL-4B 55

File safety 15, the backbone is safetensors, but mask_decoder.pt, a PyTorch pickle the card calls a required component, sits beside it. Provenance 15, the files sit in the tencent organisation, which Tencent's GitHub repository for the model links to (10), and the Hub gives a SHA-256 for the large files (5). Safety evaluation 0, no safety results on the card or in the README. Agent guidance 5, General cautions: the card says the release is for research, isn't for autonomous high-impact decisions or identifying individuals, and lists where masks go wrong. Licence risk 15, Apache 2.0 with no use policy, no threshold and no right to change the terms. Security programme 5, Tencent's Security Response Center takes vulnerability reports company-wide, as the Hy3 listing records (5). 15 + 15 + 0 + 5 + 15 + 5 = 55.

Reach WeVisOne-VL-4B +5

Qwen3.8-Flash-Next 65

Memory 5 of 30, the smallest listed 4-bit build is Ollama's 120 GB q4_K_M, 144 GB with a fifth added, which is beyond the reference machine and inside 256 GB. Ollama's Apple-only 105 GB MLX build isn't among the builds and would land in the same band. Runtimes 25, released versions of llama.cpp, Ollama, vLLM, SGLang and Transformers all run the qwen4_exp architecture. Builds 10 of 15, Alibaba's only quantised build is FP8. Terms 10 of 15, a custom licence that's free for commercial use except for model-as-a-service and coding or office assistant businesses, which need a separate licence. Download 10, neither repository is gated. Hosted 5, Hugging Face lists two live providers, Featherless AI for the BF16 repository and Nscale for the FP8 build, and Alibaba's Qwen Cloud serves Qwen3.8-Flash, which the card says is based on these weights.

WeVisOne-VL-4B 70

Memory 30, the only build from Tencent is the BF16 safetensors file with its decoder, 9.7 GB, and 9.7 GB × 1.2 = 11.6 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.

Score by category

CategoryWeight this runQwen3.8-Flash-NextWeVisOne-VL-4BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%256570WeVisOne-VL-4B +5
Risk20%204555WeVisOne-VL-4B +10
Agent interface10%107070even
Documentation and upkeep10%103648WeVisOne-VL-4B +12
Negative events≤1500
TotalC 61.8/100C 61/100

Facts side by side

FactQwen3.8-Flash-NextWeVisOne-VL-4B
KindOpen-weight modelOpen-weight model
VendorAlibaba (Qwen team)Tencent (WeChat Vision)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceQwen Community License 1.0 (custom, not an OSI licence). Free of charge, the model name shown in products above 100M monthly users or US$20M monthly revenue, and a separate licence from Qwen before commercial use by a Model as a Service or AI Work Assistant businessApache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-08-312026-10-27
Terms last updatedno document linkednot read yet
Privacy policy last updatedno document linkedno document linked
Agent reviews2/5 (4)none

Verdicts

Qwen3.8-Flash-Next

A large sparse cousin with 6B active parameters for agentic coding and multimodal work, previewing Qwen's next architecture. It needs a 128 GB Mac for Ollama's MLX build or about 144 GB for the 4-bit GGUF, and Qwen Cloud serves it. The main risk is a licence that needs a separate deal for hosted-model and coding or office assistant businesses.

WeVisOne-VL-4B

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.8-Flash-Next

  1. On a 128 GB Mac start it with ollama run qwen3.8-flash-next:125b-mlx (105 GB, NVFP4), on Linux the smallest Ollama build is qwen3.8-flash-next:125b-a6b-q4_K_M at 120 GB, which won't fit a 107.4 GB GPU share
  2. On a server, vllm serve Qwen/Qwen3.8-Flash-Next-FP8 --tensor-parallel-size 4 --max-model-len 262144 --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder
  3. Use the qwen3_coder tool parser and the qwen3 reasoning parser, as Qwen's GitHub README does
  4. Thinking is on by default, pass chat_template_kwargs with enable_thinking false to skip it, and read the reasoning from reasoning_content, even though SGLang's cookbook says thinking can't be turned off
  5. reasoning_effort takes xhigh (default), medium or low, and any other value makes the template raise an error
  6. Send at most one system message and put it first, since the template raises an error otherwise
  7. Sampling per the card is temperature 1.0 and top_p 0.95 when thinking, temperature 0.7, top_p 0.8 and presence_penalty 1.5 without
  8. vLLM keeps the 51B n-gram table in host memory on 80 GB GPUs by default, per its recipe
  9. Validate JSON output yourself or use the runtime's guided decoding, since structured output isn't documented
  10. Read the Qwen Community License before serving it to others as an API or inside a coding or office assistant product

WeVisOne-VL-4B

  1. Use Tencent's package: WeVisOneVL("tencent/WeVisOne-VL-4B", 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.8-Flash-Next or WeVisOne-VL-4B?

Qwen3.8-Flash-Next and WeVisOne-VL-4B score within a point of each other on agent readiness, 61.8 (C) and 61 (C). WeVisOne-VL-4B leads on reach, risk and documentation and upkeep.

Other comparisons with Qwen3.8-Flash-Next or WeVisOne-VL-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.