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

MiMo-V2.6-Flash-RL vs Swift 1.5 Qwen3.8-27B

MiMo-V2.6-Flash-RL and Swift 1.5 Qwen3.8-27B score within a point of each other on agent readiness, 61 (C) and 61 (C). Swift 1.5 Qwen3.8-27B leads on reach and risk. 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

MiMo-V2.6-Flash-RL C

Best for Teams with a GPU server, or a provider account, that want an open agent model with a very long context

Ahead on

  • Agent interface, 85 against 60
  • Documentation and upkeep, 59 against 43

Watch for

178 GB at 4 bits, so it needs about 200 GB of memory

Swift 1.5 Qwen3.8-27B C

Best for Agents on a 24 to 32 GB GPU or Mac that want Qwen3.8-27B's skills with shorter thinking, for teams under US$1M revenue or research.

Ahead on

  • Reach, 80 against 65
  • Risk, 50 against 45

Watch for

Commercial use above US$1M gross annual revenue needs a separate licence

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.

Agent interface MiMo-V2.6-Flash-RL +25

MiMo-V2.6-Flash-RL 85

Chat template 20, chat_template.jinja in the repository (3,868 characters), with a copy in tokenizer_config.json. Tool-calling format 25, the card names the parser to use in two runtimes: the mimo tool-call parser in SGLang and in vLLM, with auto tool choice, and both ship it in a release. Trained tool calling 20, the card describes reinforcement learning on coding and general agent tasks across several harnesses, and the template renders every call in a turn. Structured output 0, Nothing on the card about JSON or schema-constrained output. Reasoning control 10, the template has an enable_thinking switch and keeps reasoning_content, and the card names the mimo reasoning parser for SGLang and vLLM, which returns the reasoning apart from the answer. Context 10, 1M tokens per the card's model summary, and 1,048,576 positions in config.json. 20 + 25 + 20 + 0 + 10 + 10 = 85.

Swift 1.5 Qwen3.8-27B 60

Chat template 20, the base's Jinja file. Tool-calling format 10 of 25, the format is only in the template and the parser only in serving commands. Trained tool calling 20, several calls a turn and agentic post-training. Structured output 0, not documented. Reasoning control 0, the card mentions reasoning_effort but not how to set it, turn thinking off or read the reasoning. Context 10, 262,144 tokens native.

Documentation and upkeep MiMo-V2.6-Flash-RL +16

MiMo-V2.6-Flash-RL 59

Model card 14, Intended use, the architecture, the parameters, the context and the languages (in the metadata) are on the card. Training data 5, A description of the training method with no data sources, sizes or cut-off. Last change 20, the last commits, on 28 October 2026, updated the card, 13 days before this check. Responsiveness 5, Of the 13 most recent discussions that aren't pull requests (21 September to 6 November 2026), 3 have a reply from a XiaomiMiMo member, which is a few. Version policy 5, MiMo-V2.5 stays in its own repositories and V2.6 came out in new ones, with no dated note on the older cards that we read. File health 10, Config, template and card agree on the architecture and the 1M context, and two early faults (invalid JSON in the draft model's config, preprocessor values) were fixed in commits that say so. 14 + 5 + 20 + 5 + 5 + 10 = 59.

Swift 1.5 Qwen3.8-27B 43

Model card 8 of 20, intended use, parameters and context only. Training data 5, a general description with no cut-off. Last change 20, UkisAI's own ONNX builds of the model took a new card and licence on 8 October, 26 days ago (the main repository's last commit is the 3 October README update). Responsiveness 0, UkisAI answered none of 8 discussions. Version policy 5, Swift 1.0 stays in its own repository without a note. File health 5, reports of a broken model wait without a reply and the card's metadata claims a gate that doesn't exist.

Reach Swift 1.5 Qwen3.8-27B +15

MiMo-V2.6-Flash-RL 65

Memory 5, the smallest build at 4 bits or better is ggml-org's MXFP4 GGUF, 168.93 GB with its projector, and 168.93 GB × 1.2 = 202.7 GB, within 256 GB. Xiaomi's own files are 177.74 GB. ggml-org's Q2_K is below 4 bits and isn't read. Runtimes 20, Released vLLM 0.33.0 and SGLang 0.5.23 have the mimo_v2 model and the mimo parsers, Transformers 5.22.2 has a mimo_v2_flash model, and llama.cpp b12242 has the architecture, with a GGUF from its own organisation. Builds 10, one precision from Xiaomi, the 4-bit files it releases. Terms 15, MIT in the card's metadata, an OSI licence. Download 10, the Hub API reports gated false on 10 November 2026, so the files download with no account and nothing to accept. Hosted 5, the card says it is on Xiaomi's MiMo Open Platform API and on OpenRouter, and Novita is live for it on Hugging Face. 5 + 20 + 10 + 15 + 10 + 5 = 65.

Swift 1.5 Qwen3.8-27B 80

Memory 25 of 30, UkisAI's 4-bit MLX build is 15.9 GB and its 4-bit GGUF with the vision projector 16.4 GB, both under 20 GB with a fifth added, which fits 24 GB. Runtimes 20, the architecture is Qwen3.8-27B's, which released llama.cpp, vLLM, SGLang and Transformers run, while Ollama's entry is the base's. Builds 15, GGUF, INT4, NVFP4, FP8 and MLX builds from UkisAI. Terms 10, a custom licence that is free for commercial use below US$1M revenue. 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.

Risk Swift 1.5 Qwen3.8-27B +5

MiMo-V2.6-Flash-RL 45

File safety 5, the weights are safetensors, but the dflash folder's mask_embedding.pt is a pickle beside them (15). Provenance 15, the files sit in the XiaomiMiMo organisation, which mimo.xiaomi.com links to per the Distill listing (10). Safety evaluation 0, no safety results on the card. Agent guidance 5, General cautions only. Licence risk 15, MIT has no use policy, threshold or change clause. Security programme 5, Xiaomi runs a company security centre for reporting flaws, as read for the Distill listing (5). 5 + 15 + 0 + 5 + 15 + 5 = 45.

Swift 1.5 Qwen3.8-27B 50

File safety 25, safetensors only and nothing from the repository runs. Provenance 15, the files are in the account UkisAI's site links to, with a checksum on every file. Safety evaluation 0, none published. Agent guidance 0, nothing on prompt injection, refusals or safeguards. Licence risk 10, a revenue threshold. Security programme 0, no way to report a flaw was found.

Score by category

CategoryWeight this runMiMo-V2.6-Flash-RLSwift 1.5 Qwen3.8-27BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%256580Swift 1.5 Qwen3.8-27B +15
Risk20%204550Swift 1.5 Qwen3.8-27B +5
Agent interface10%108560MiMo-V2.6-Flash-RL +25
Documentation and upkeep10%105943MiMo-V2.6-Flash-RL +16
Negative events≤1500
TotalC 61/100C 61/100

Facts side by side

FactMiMo-V2.6-Flash-RLSwift 1.5 Qwen3.8-27B
KindOpen-weight modelOpen-weight model
VendorXiaomi (MiMo team)UkisAI
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceMIT (metadata only, no LICENSE file)Swift Open License v1.0 (custom, not an OSI licence) on UkisAI's changes, free for commercial use below US$1M gross annual revenue with a separate Swift Enterprise License above it. Built on Qwen3.8-27B, whose Apache 2.0 still governs the base
Read-only variant documentednono
llms.txtnono
Last release2026-10-282026-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 reviewsnone2.3/5 (4)

Verdicts

MiMo-V2.6-Flash-RL

A large agent model with an open licence: text, images, video and audio, a 1M context, tool calling it was trained for, and code in four released runtimes. It's a server model, 178 GB at 4 bits, and the card's commands run the repository's code. No safety results, little said about data, and few questions answered.

Swift 1.5 Qwen3.8-27B

A Qwen3.8-27B cousin post-trained to think in fewer tokens, for coding and agent work with images in, that fits a 24 GB machine with UkisAI's own 4-bit builds. Commercial use is free only below US$1M revenue. The main risks are that nobody at UkisAI answers its discussions, and that the shorter thinking rests on UkisAI's own benchmarks.

Before you call either

MiMo-V2.6-Flash-RL

  1. Plan for a provider unless you have a multi-GPU server: Xiaomi's API platform, OpenRouter or Novita
  2. On SGLang or vLLM pass --tool-call-parser mimo --reasoning-parser mimo
  3. Use temperature 1.0 and top_p 0.95, as the card recommends
  4. The card's commands pass trust-remote-code. Read the repository's three Python files first, or use Transformers 5.22.2, which has the model built in
  5. Skip the dflash folder unless you need speculative decoding. Its mask_embedding.pt is a pickle
  6. The Use Restrictions section asks for human oversight of high-risk actions

Swift 1.5 Qwen3.8-27B

  1. Quickest start is llama-server -hf ukisai/Swift-1.5-Qwen3.8-27B-GGUF:Q4_K_M --jinja, about 18.4 GB with the vision projector
  2. On our reference machine BF16 fits, vllm serve ukisai/Swift-1.5-Qwen3.8-27b --max-model-len 262144 --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder
  3. The template is Qwen3.8-27B's, so chat_template_kwargs with reasoning_effort low, medium or xhigh (default) and enable_thinking false work as on the base
  4. UkisAI benchmarked it at temperature 1.0, top_p 0.95, top_k 20 and presence_penalty 0, which is a reasonable starting point
  5. The MLX 4-bit build needs UkisAI's patched MLX-LM and has no image or video chat
  6. Check the licence before commercial use, it stops at US$1M gross annual revenue including affiliates
  7. MTP self-speculative decoding is available with the base's head, flags on the card

Questions

Which is better for AI agents, MiMo-V2.6-Flash-RL or Swift 1.5 Qwen3.8-27B?

MiMo-V2.6-Flash-RL and Swift 1.5 Qwen3.8-27B score within a point of each other on agent readiness, 61 (C) and 61 (C). Swift 1.5 Qwen3.8-27B leads on reach and risk.

Other comparisons with MiMo-V2.6-Flash-RL or Swift 1.5 Qwen3.8-27B

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.