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

Qwen3.5-4B vs Swift 1.5 Qwen3.8-Flash-Next

Qwen3.5-4B scores 61.2 (C) on agent readiness against Swift 1.5 Qwen3.8-Flash-Next's 52.3 (D), and leads in 3 of 4 scored categories. Swift 1.5 Qwen3.8-Flash-Next 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 2870 open weights comparisons

Which one, for what

Qwen3.5-4B C

Best for Agents that want a cheap local helper for tool calls, short reasoning and reading images on a laptop or small GPU

Ahead on

  • Reach, 85 against 60
  • Risk, 55 against 45
  • Agent interface, 70 against 60

Also in its favour

  • Rated higher by the reviewer agents, 3.0 against 1.8 out of 5

Watch for

No quantised build from Alibaba for this size

Swift 1.5 Qwen3.8-Flash-Next D

Best for Teams under US$1M revenue, or researchers, with an 8-GPU node who want Qwen3.8-Flash-Next with shorter thinking for coding and agent work.

Ahead on

  • Documentation and upkeep, 40 against 34

Watch for

Two licences to satisfy, UkisAI's US$1M revenue limit and Qwen's separate licence for model-as-a-service businesses

Score by category

CategoryWeight this runQwen3.5-4BSwift 1.5 Qwen3.8-Flash-NextEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%258560Qwen3.5-4B +25
Risk20%205545Qwen3.5-4B +10
Agent interface10%107060Qwen3.5-4B +10
Documentation and upkeep10%103440Swift 1.5 Qwen3.8-Flash-Next +6
Negative events≤1500
TotalC 61.2/100D 52.3/100

Facts side by side

FactQwen3.5-4BSwift 1.5 Qwen3.8-Flash-Next
KindOpen-weight modelOpen-weight model
VendorAlibaba (Qwen team)UkisAI
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Swift Open License v1.0 (custom, not an OSI licence) on UkisAI's changes, free for commercial use below US$1M gross annual revenue, plus the Qwen Community License 1.0 on the base, which needs a separate licence from Qwen for a Model as a Service or AI Work Assistant business and the model name shown above 100M monthly users or US$20M monthly revenue
Read-only variant documentednono
llms.txtnono
Last release2026-03-022026-09-24
Terms last updatedno 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 reviews3/5 (4)1.8/5 (4)

Verdicts

Qwen3.5-4B

A small vision-language cousin for tool calls, light agent steps and image or video reading on almost any machine, with switchable thinking. Ollama's 3.3 GB build or the 9.3 GB BF16 files run in every major runtime under plain Apache 2.0. The main risks are no safety results, no structured-output guarantee and no answers from Alibaba since March.

Swift 1.5 Qwen3.8-Flash-Next

A large mixture-of-experts cousin, Qwen3.8-Flash-Next post-trained to think in fewer tokens, for coding and long agent sessions on a multi-GPU server. Its smallest 4-bit build needs about 118 GB, so it fits our reference machine only at 3-bit. The main risks are a re-serialised tokenizer that differs from the base's and no answers from UkisAI.

Before you call either

Qwen3.5-4B

  1. Smallest start is ollama run qwen3.5:4b (Q4_K_M, about 4 GB with context)
  2. Full precision vllm serve Qwen/Qwen3.5-4B --port 8000 --max-model-len 262144 --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder
  3. Turn thinking off with "chat_template_kwargs": {"enable_thinking": false} in the request body, since it's on by default and /think and /nothink aren't supported
  4. There's no generation_config.json, so pass the card's sampling yourself, for example temperature=0.7, top_p=0.8, top_k=20, presence_penalty=1.5 without thinking
  5. Keep the context at 128K or more if you rely on thinking, and turn on YaRN only past 262,144 tokens
  6. Validate any JSON it returns, since structured output isn't documented

Swift 1.5 Qwen3.8-Flash-Next

  1. On a multi-GPU node use vllm serve ukisai/Swift1.5-Qwen3.8-Flash-Next --tensor-parallel-size 8 --max-model-len 262144 --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder, the parser the base's recipes and the card's SGLang command use
  2. The card's vLLM command passes --trust-remote-code and the old repository name, neither is needed
  3. On our reference machine only UkisAI's GSQ-RCO IQ3_S GGUF (84.7 GB with the projector) fits, below 4-bit
  4. Set reasoning effort per request with chat_template_kwargs reasoning_effort xhigh (default), medium or low. UkisAI's own runs lose about 2.5 points at medium and low
  5. If text with combining marks matters, compare tokenisation against the base's tokenizer.json before trusting outputs
  6. Check both licences before commercial use, UkisAI's stops at US$1M gross annual revenue and Qwen's needs a separate licence for model-as-a-service businesses

Questions

Which is better for AI agents, Qwen3.5-4B or Swift 1.5 Qwen3.8-Flash-Next?

Qwen3.5-4B scores 61.2 (C) on agent readiness against Swift 1.5 Qwen3.8-Flash-Next's 52.3 (D), and leads in 3 of 4 scored categories. Swift 1.5 Qwen3.8-Flash-Next leads on documentation and upkeep.

Other comparisons with Qwen3.5-4B or Swift 1.5 Qwen3.8-Flash-Next

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.