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

Hy-Memory-30B-A3B vs Swift 1.5 Qwen3.8-Flash-Next

Hy-Memory-30B-A3B scores 61 (C) on agent readiness against Swift 1.5 Qwen3.8-Flash-Next's 54.2 (C), and leads in every scored category. 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

Hy-Memory-30B-A3B C

Best for Agents with an external memory framework that want a local model for the write path on a 24 GB card

Ahead on

  • Reach, 85 against 65
  • Risk, 60 against 45
  • Agent interface, 65 against 60
  • Documentation and upkeep, 68 against 40

Watch for

Not a general assistant or a tool caller

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.

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

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 Hy-Memory-30B-A3B +28

Hy-Memory-30B-A3B 68

Model card 8, Intended use (the write path of Mem0, MemOS and Hy-Memory), parameters (30B, about 3B active) and languages (English and Chinese, in the metadata) are there. Training data 5, A general description of the two training stages inside the harnesses, with no datasets, sizes or cut-off. Last change 20, the last commit, on 16 October 2026, added the licence and the card, 25 days before this check. Responsiveness 20, Of the 4 discussions that aren't pull requests (16 to 30 October 2026), 3 have a reply from a tencent organisation member. Version policy 5, A first release, with nothing replaced. File health 10, Config, tokenizer and template agree on the architecture, the context and the thinking levels. 8 + 5 + 20 + 20 + 5 + 10 = 68.

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 Hy-Memory-30B-A3B +20

Hy-Memory-30B-A3B 85

Memory 25, Tencent's own Q4_K_M GGUF is 18.24 GB, and 18.24 GB × 1.2 = 21.9 GB, which fits 24 GB but not 16 GB. Its Q3_K_M file and the two files with experts at 1 or 2 bits are below 4-bit precision and don't count. Runtimes 20, hy_v3 model code in released vLLM (HYV3ForCausalLM in the v0.33.0 registry), SGLang v0.5.23 (hunyuan_v3.py), Transformers v5.22.2 and llama.cpp b12242, 5 each. Builds 15, Tencent publishes an FP8 repository and a GGUF repository with Q4_K_M, Q6_K and Q8_0 files in its own organisation, so quantised builds at two precisions or more. Terms 15, Apache 2.0, with only a preamble naming Tencent as copyright holder above the licence text. Download 10, gated is false for the main, FP8 and GGUF repositories on 10 November 2026, so the files download with no account or terms to accept. Hosted 0, Hugging Face lists no inference provider for the model (an empty provider mapping on 10 November 2026), and the card names no API. 25 + 20 + 15 + 15 + 10 + 0 = 85.

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.

Risk Hy-Memory-30B-A3B +15

Hy-Memory-30B-A3B 60

File safety 25, 51 safetensors shards and no pickle or Python files. Provenance 15, files in the tencent organisation that the card's own resource list links to (10), with a SHA-256 listed for all 53 large files (5). Safety evaluation 0, no safety results on the card. Agent guidance 0, no prompt-injection guidance, instruction hierarchy, account of trained refusals or general cautions on the card. Licence risk 15, Apache 2.0 with no use policy, no field-of-use limit, no threshold and no clause letting Tencent change the terms. Security programme 5, Tencent's Security Response Center takes vulnerability reports company-wide with published reward rules, as the Hy3 listing records (5). 25 + 15 + 0 + 0 + 15 + 5 = 60.

Swift 1.5 Qwen3.8-Flash-Next 45

File safety 25, safetensors only and no code in the repository, though the card's vLLM command passes trust-remote-code. 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 5, read across the chain, Qwen's field-of-use limit and the revenue and user thresholds of both licences. Security programme 0, no way to report a flaw was found.

Agent interface Hy-Memory-30B-A3B +5

Hy-Memory-30B-A3B 65

Chat template 20, chat_template.jinja in the repository. Tool-calling format 10, the card doesn't mention tools. Trained tool calling 10, the template can render tool calls, but the card presents the model as a memory writer that returns memories as text or JSON and says nothing of calling tools. Structured output 5, the card's quickstart asks for a JSON object with a memories list in the system prompt and shows nothing else, no response_format and no schema, so JSON output is shown by example without a documented way to constrain it. Reasoning control 10, the card passes reasoning_effort as no_think per request through chat_template_kwargs, and the template takes high, low or no_think. Context 10, 262,144 tokens native (max_position_embeddings in config.json). 20 + 10 + 10 + 5 + 10 + 10 = 65.

Swift 1.5 Qwen3.8-Flash-Next 60

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

Score by category

CategoryWeight this runHy-Memory-30B-A3BSwift 1.5 Qwen3.8-Flash-NextEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%258565Hy-Memory-30B-A3B +20
Risk20%206045Hy-Memory-30B-A3B +15
Agent interface10%106560Hy-Memory-30B-A3B +5
Documentation and upkeep10%106840Hy-Memory-30B-A3B +28
Negative events≤1500
TotalC 61/100C 54.2/100

Facts side by side

FactHy-Memory-30B-A3BSwift 1.5 Qwen3.8-Flash-Next
KindOpen-weight modelOpen-weight model
VendorTencent (Hy 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-10-162026-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

Hy-Memory-30B-A3B

A specialist that writes an agent's long-term memory, built to slot into Mem0, MemOS or Tencent's own framework in place of a general model. It fits a 24 GB card from Tencent's own GGUF, under plain Apache 2.0, and Tencent answers on the repository. Its results are Tencent's own and nobody has rerun them.

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

Hy-Memory-30B-A3B

  1. Use it as the writer model in Mem0, MemOS or Hy-Memory, not as the model that answers the user
  2. Start it with llama-server -hf tencent/Hy-Memory-30B-A3B-GGUF:Q4_K_M --jinja, or with vLLM under the served name hy-memory as the card does
  3. Pass reasoning_effort as no_think in chat_template_kwargs and temperature 0, as the card's example does
  4. Ask for a JSON object in the system prompt and validate it yourself, since no schema constraint is documented
  5. Treat what it stores as unverified. It keeps what a conversation says, true or not

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, Hy-Memory-30B-A3B or Swift 1.5 Qwen3.8-Flash-Next?

Hy-Memory-30B-A3B scores 61 (C) on agent readiness against Swift 1.5 Qwen3.8-Flash-Next's 54.2 (C), and leads in every scored category.

Other comparisons with Hy-Memory-30B-A3B 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.