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

Ling-3.1-flash-1019 vs Swift 1.5 Qwen3.8-Flash-Next

Ling-3.1-flash-1019 and Swift 1.5 Qwen3.8-Flash-Next score within a point of each other on agent readiness, 54.8 (C) and 54.2 (C). Swift 1.5 Qwen3.8-Flash-Next 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

Ling-3.1-flash-1019 C

Best for Teams with a multi-GPU server that want an MIT-licensed flagship for long agent runs and coding

Ahead on

  • Documentation and upkeep, 56 against 40

Watch for

574 GB in FP8 with no smaller build from inclusionAI, so no single machine under 690 GB of GPU memory runs it

Swift 1.5 Qwen3.8-Flash-Next C

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

  • Reach, 65 against 60

Watch for

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

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 Ling-3.1-flash-1019 +16

Ling-3.1-flash-1019 56

Model card 11, Intended use (complex reasoning, multi-step tasks and agentic workflows), architecture, parameters (560B total, 25B active) and context (1M claimed) are on the card. Training data 15, the training-content summary the card links names the source categories (Common Crawl and other public datasets, commercially licensed data, the Ant Spider crawler, synthetic data), the size band (over 10 trillion text tokens), data collected up to about July 2026 and the filtering, without listing datasets with sizes. Last change 20, the newest commit, on 4 November 2026, edited the card, six days before this check, and the files went up on 27 October. Responsiveness 0, Neither of the 2 discussions that aren't pull requests (both opened on 27 October 2026) has a reply from an inclusionAI member. Version policy 5, the update went into a repository of its own and Ling-3.1-flash and Ling 3.0 stay in theirs. File health 5, the card states a 1M-token context while config.json gives 262,144 with no rope scaling, and its serve commands name the earlier repository as the model path. 11 + 15 + 20 + 0 + 5 + 5 = 56.

Swift 1.5 Qwen3.8-Flash-Next 40

Model card 5 of 20, intended use and context only. Training data 5, a general description with no cut-off. Last change 20, UkisAI added an IQ3_S tier to its GSQ-RCO GGUF build on 7 October 2026, 28 days before this check; the main repository's only commit is the 24 September release. Responsiveness 0, UkisAI answered none of 3 discussions. Version policy 5, a first release, renamed without a note. File health 5, the re-serialised tokenizer splits text differently from the repository's own tokenizer config and the base. 5 + 5 + 20 + 0 + 5 + 5 = 40.

Reach Swift 1.5 Qwen3.8-Flash-Next +5

Ling-3.1-flash-1019 60

Memory 0, inclusionAI's only build is the FP8 release at 573.78 GB, × 1.2 = 688.5 GB, above 256 GB, and no runtime's library has a build. Runtimes 25, Released model code in Transformers 5.22.2 (bailing_hybrid), vLLM 0.33.0 (BailingMoeV3ForCausalLM, with ling3 tool and reasoning parsers), SGLang 0.5.23 (bailing_moe_v3.py, its bailing_hybrid config and MTP module) and llama.cpp b12242 (bailingmoe3), and Ollama, credited through its pinned llama.cpp as on the Ling-3.0-tiny listing: v0.40.16 sets LLAMA_CPP_VERSION to b12177. Builds 10, the release is FP8, the one quantised precision inclusionAI publishes for it. Terms 15, MIT in the card's metadata, with no use policy or other terms added on the card or in the repository. Download 10, the Hub API's model info gives gated false on 10 November 2026, so the files download with no account and no terms to accept. Hosted 0, the Hub API's provider mapping is empty for this repository on 10 November 2026. 0 + 25 + 10 + 15 + 10 + 0 = 60.

Swift 1.5 Qwen3.8-Flash-Next 65

Memory 5 of 30, the smallest 4-bit build is UkisAI's IQ4_XS GGUF at 98.6 GB with the vision projector, 118.3 GB with a fifth, above the reference machine's GPU share and within 256 GB. Runtimes 25, the architecture is Qwen3.8-Flash-Next's (qwen4_exp), which released llama.cpp, vLLM, SGLang and Transformers run, and Ollama runs it through its pinned llama.cpp (b11963 in v0.40.14), this run's reading for Ollama. Builds 15, GGUF, INT4 and NVFP4 builds from UkisAI. Terms 10, two custom licences that allow commercial use within limits. Download 10, not gated. Hosted 0, no provider serves it, and UkisAI's research API on the card couldn't be shown to serve it, since robots.txt disallows calling it. 5 + 25 + 15 + 10 + 10 + 0 = 65.

Score by category

CategoryWeight this runLing-3.1-flash-1019Swift 1.5 Qwen3.8-Flash-NextEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%256065Swift 1.5 Qwen3.8-Flash-Next +5
Risk20%204545even
Agent interface10%106060even
Documentation and upkeep10%105640Ling-3.1-flash-1019 +16
Negative events≤1500
TotalC 54.8/100C 54.2/100

Facts side by side

FactLing-3.1-flash-1019Swift 1.5 Qwen3.8-Flash-Next
KindOpen-weight modelOpen-weight model
VendorinclusionAI (Ant Group)UkisAI
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceMITSwift 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-11-042026-09-24
Terms last updatedno document linkedno date given
Privacy policy last updatedno document linkedno document linked
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetnot found in the text
Terms or service can change without noticenot read yetnot found in the text
Arbitration or class-action waivernot read yetnot found in the text
Agent reviewsnone1.8/5 (4)

How the scores have moved

Verdicts

Ling-3.1-flash-1019

inclusionAI's newest flagship, a 560B hybrid mixture of experts under plain MIT that vLLM, SGLang, Transformers and llama.cpp run in released versions. It ships only as 574 GB of FP8, so it needs a multi-GPU server. The card overstates the context, documents little about tool calls, and has no safety results.

Swift 1.5 Qwen3.8-Flash-Next

A mixture-of-experts vision-language model, 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

Ling-3.1-flash-1019

  1. Serve it with SGLang 0.5.23 or later on 8 H200 or 4 GB300 GPUs, per the card, and use this repository's name as the model path, not the earlier one the card's command shows
  2. With vLLM pass --trust-remote-code, --tool-call-parser ling3 and --reasoning-parser ling3
  3. Set chat_template_kwargs enable_thinking false for direct answers. Reasoning comes back in reasoning_content per SGLang's cookbook
  4. Plan on 262,144 tokens of context. The 1M figure needs the YaRN override in SGLang's cookbook
  5. Use temperature 1.0, top_p 0.95 and top_k 20, per the card
  6. Validate JSON output yourself, 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, Ling-3.1-flash-1019 or Swift 1.5 Qwen3.8-Flash-Next?

Ling-3.1-flash-1019 and Swift 1.5 Qwen3.8-Flash-Next score within a point of each other on agent readiness, 54.8 (C) and 54.2 (C). Swift 1.5 Qwen3.8-Flash-Next leads on reach.

Other comparisons with Ling-3.1-flash-1019 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.