Head to head · Open-weight models you run yourself · October 2026 research run
Cola2 vs Hy-Memory-30B-A3B
Hy-Memory-30B-A3B scores 61 (C) on agent readiness against Cola2's 33.9 (F), 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
Cola2 F
Best for Researchers working on latent or diffusion language models who want a checkpoint to study
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
No licence stated for the weights
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 25
- Risk, 60 against 40
- Agent interface, 65 against 20
- Documentation and upkeep, 68 against 58
Watch for
Not a general assistant or a tool caller
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.
Reach Hy-Memory-30B-A3B +60
Cola2 25
Memory 15, the only build is the F32 safetensors set, 35.07 GB, and 35.07 GB × 1.2 = 42.1 GB, within 64 GB. Loaded as BF16, as the card's example does, it needs about half, but the line reads the file size. Runtimes 0, none of the six runs it in a released version. Builds 0, one set of weights and no quantised build. Terms 0, no licence for the weights. 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, and nothing names an API that serves it. 15 + 0 + 0 + 0 + 10 + 0 = 25.
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.
Agent interface Hy-Memory-30B-A3B +45
Cola2 20
Chat template 20, A chat template in tokenizer_config.json (4,116 characters), which came with the Qwen3 tokenizer. Tool-calling format 0, none. Trained tool calling 0, not trained for tool calling. Structured output 0, Nothing about JSON or schema-constrained output. Reasoning control 0, no reasoning mode. Context 0, no context length is stated. 20 + 0 + 0 + 0 + 0 + 0 = 20.
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.
Risk Hy-Memory-30B-A3B +20
Cola2 40
File safety 15, safetensors only, no .bin, .pt or .pth files (25). Provenance 15, the files sit in the ByteDance-Seed organisation, which the ByteDance-Seed GitHub repository for the model links to (10). Safety evaluation 0, no safety results. Agent guidance 5, General cautions in the GitHub model card: not instruction-tuned or safety-aligned, not for use as an assistant, for facts or advice, or for high-impact decisions about people. Licence risk 0, With no licence for the weights there is nothing to hold ByteDance to. Security programme 5, the GitHub repository's SECURITY.md sends reports to ByteDance's security centre and says how they're assessed (5). 15 + 15 + 0 + 5 + 0 + 5 = 40.
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.
Documentation and upkeep Hy-Memory-30B-A3B +10
Cola2 58
Model card 8, Intended use and limitations (the out-of-scope list, and the unconverged latent model) and the architecture are on the card and the GitHub model card it links. Training data 15, the GitHub model card names the source (OLMo 2 pretraining text, retokenised) and the mix by stage with token counts, 346.03B in all. Last change 20, All six commits are from 6 November 2026, four days before this check, the last one updating a checksum in the README. Responsiveness 0, no discussions on the repository, so nobody has asked anything yet and the line reads as none answered, as settled in calibration. Version policy 5, A first release. File health 10, Config, files and card agree: F32 weights, a float32 config and a card that says to load them as bfloat16, with SHA256SUMS to check the download. 8 + 15 + 20 + 0 + 5 + 10 = 58.
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.
Score by category
| Category | Weight this run | Cola2 | Hy-Memory-30B-A3B | Edge |
|---|---|---|---|---|
| Capability | 35%pending | pending | pending | not scored in this run |
| Reach | 25%25 | 25 | 85 | Hy-Memory-30B-A3B +60 |
| Risk | 20%20 | 40 | 60 | Hy-Memory-30B-A3B +20 |
| Agent interface | 10%10 | 20 | 65 | Hy-Memory-30B-A3B +45 |
| Documentation and upkeep | 10%10 | 58 | 68 | Hy-Memory-30B-A3B +10 |
| Negative events | ≤15 | 0 | 0 | |
| Total | F 33.9/100 | C 61/100 |
Facts side by side
| Fact | Cola2 | Hy-Memory-30B-A3B |
|---|---|---|
| Kind | Open-weight model | Open-weight model |
| Vendor | ByteDance (Seed) | Tencent (Hy team) |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | ||
| Auth | None | None |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | None stated for the weights (the code is Apache 2.0) | Apache-2.0 |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | 2026-11-06 | 2026-10-16 |
| Terms last updated | no document linked | no document linked |
| Privacy policy last updated | no document linked | no document linked |
Verdicts
Cola2
A research release, and an honest one: ByteDance Seed says it's a base model with an unconverged latent stage, scoring below Llama-3-8B on its own table. It's here for people studying continuous-latent generation. Agents can't use it as a model: 32-token completions, no chat or tools, the repository's own code to load it, and no licence on the weights.
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.
Before you call either
Cola2
- Don't plan to use this as your model. It completes short prompts and wasn't tuned to follow instructions
- Don't use it commercially on the strength of this listing. The weights have no stated licence
- If you study it, read modeling_cola2.py first: trust_remote_code runs it
- Pin Transformers below 5, as the card requires
- Pass a seeded torch.Generator to generate(). Output varies between runs even with greedy decoding
- Check the download with
sha256sum -c SHA256SUMS
Hy-Memory-30B-A3B
- Use it as the writer model in Mem0, MemOS or Hy-Memory, not as the model that answers the user
- 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 - Pass
reasoning_effortas no_think inchat_template_kwargsand temperature 0, as the card's example does - Ask for a JSON object in the system prompt and validate it yourself, since no schema constraint is documented
- Treat what it stores as unverified. It keeps what a conversation says, true or not
Questions
Which is better for AI agents, Cola2 or Hy-Memory-30B-A3B?
Hy-Memory-30B-A3B scores 61 (C) on agent readiness against Cola2's 33.9 (F), and leads in every scored category.
Other comparisons with Cola2 or Hy-Memory-30B-A3B
- Agents-A1-4B vs Cola2
- Agents-A1-4B vs Hy-Memory-30B-A3B
- Apertus v1.5 8B vs Cola2
- Apertus v1.5 8B vs Hy-Memory-30B-A3B
- Apodex-1.1-mini vs Cola2
- Apodex-1.1-mini vs Hy-Memory-30B-A3B
- Arete-27B vs Cola2
- Arete-27B vs Hy-Memory-30B-A3B
- BigBang-v1 vs Cola2
- BigBang-v1 vs Hy-Memory-30B-A3B
- Carbon-X vs Cola2
- Carbon-X vs Hy-Memory-30B-A3B
- Cola2 vs Cosmos-Reason2-2B
- Cola2 vs Darwin-36B-Opus
- Cola2 vs DeepSeek-V3.2
- Cola2 vs DeepSeek V4.1 Flash
- Cola2 vs DeepSeek-V4-Flash-0731
- Cola2 vs Devstral Small 2
- Cola2 vs DiffusionGemma 26B A4B IT
- Cola2 vs EXAONE 4.5 33B
- Cola2 vs Gemma 4 12B IT
- Cola2 vs Gemma 4 26B A4B IT
- Cola2 vs Gemma 4 31B IT
- Cola2 vs Gemma 4 E2B IT
- Cola2 vs Gemma 4 E4B IT
- Cola2 vs GLM-4.5-Air
- Cola2 vs GLM-4.7-Flash
- Cola2 vs GLM-5.3
- Cola2 vs GLM-5.3-Flash
- Cola2 vs gpt-oss-120b
- Cola2 vs gpt-oss-20b
- Cola2 vs Granite 4.2 30B
- Cola2 vs Granite 4.2 3B
- Cola2 vs Granite 4.2 8B
- Cola2 vs Hy3
- Cola2 vs Inkling
- Cola2 vs Inkling-Small
- Cola2 vs InternVL3.5-GPT-OSS-20B-A4B-Preview
- Cola2 vs Kimi K3
- Cola2 vs Kimi K3.1 Pro
- Cola2 vs Kolibri-1
- Cola2 vs Kronos
- Cola2 vs Laguna M.1
- Cola2 vs Laguna S 2.1
- Cola2 vs Laguna XS 2.1
- Cola2 vs LBS-27B
- Cola2 vs LFM2.5-2.6B
- Cola2 vs LFM3-1.7B
- Cola2 vs LFM3-Audio-2B
- Cola2 vs LFM3-Omni-2B
- Cola2 vs LFM3-VL-2B
- Cola2 vs Ling-3.0-tiny
- Cola2 vs Ling-3.1-flash-1019
- Cola2 vs LongCat-2.5
- Cola2 vs MiMo-V2.6 Distill Qwen 9B
- Cola2 vs MiMo-V2.6-Flash-RL
- Cola2 vs MiniCPM-o 4.5
- Cola2 vs MiniCPM-V 4.7 1B
- Cola2 vs MiniCPM-V 4.7 35B-A3B
- Cola2 vs MiniCPM5-2B
- Cola2 vs MiniMax-M2.5
- Cola2 vs MiniMax-M2.7
- Cola2 vs MiniMax-M3.1-Flash
- Cola2 vs Mistral Large 4
- Cola2 vs Muse Glimmer 30B
- Cola2 vs Nanbeige4.2-3B
- Cola2 vs Nanbeige4.3-33B
- Cola2 vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- Cola2 vs Nemotron 3.5 Lightning 30B A3B
- Cola2 vs Nemotron 3 Nano 30B A3B
- Cola2 vs Nemotron 3 Nano 4B
- Cola2 vs Nemotron 3 Nano Omni 30B A3B Reasoning
- Cola2 vs Nemotron 3 Super 120B A12B
- Cola2 vs Nemotron 3 Ultra 550B A55B
- Cola2 vs North Mini Code 1.0
- Cola2 vs occamy-1.0
- Cola2 vs Olmo 3 7B Think
- Cola2 vs Ornith-1.5-122B
- Cola2 vs Ornith-1.5-35B-A3B
- Cola2 vs Ornith-1.5-397B
- Cola2 vs Ornith-1.5-9B
- Cola2 vs OTel-2.0-LLM-31B-IT
- Cola2 vs Qwen-AgentWorld-35B-A3B
- Cola2 vs Qwen3-30B-A3B-Instruct-2507
- Cola2 vs Qwen3-4B-Instruct-2507
- Cola2 vs Qwen3.5-0.8B
- Cola2 vs Qwen3.5-122B-A10B
- Cola2 vs Qwen3.5-2B
- Cola2 vs Qwen3.5-397B-A17B
- Cola2 vs Qwen3.5-4B
- Cola2 vs Qwen3.5-9B
- Cola2 vs Qwen3.6-27B
- Cola2 vs Qwen3.6-35B-A3B
- Cola2 vs Qwen3.8-27B
- Cola2 vs Qwen3.8-Flash-Next
- Cola2 vs Qwen3-Coder-30B-A3B-Instruct
- Cola2 vs Qwen3-Coder-Next
- Cola2 vs Qwen3-Omni-30B-A3B-Instruct
- Cola2 vs Qwen3-VL-2B-Instruct
- Cola2 vs Qwen3-VL-30B-A3B-Instruct
- Cola2 vs Qwen3-VL-32B-Instruct
- Cola2 vs Qwen3-VL-4B-Instruct
- Cola2 vs Qwen3-VL-8B-Instruct
- Cola2 vs Qwopus3.8-27B-Flash-V2
- Cola2 vs Recursive Flint
- Cola2 vs Ripple-65B Preview
- Cola2 vs SenseNova-Loop-9B-Preview
- Cola2 vs SmolLM3-3B
- Cola2 vs Spark-X2.6-4B
- Cola2 vs Step 3.7 Flash
- Cola2 vs Swift 1.5 Qwen3.8-27B
- Cola2 vs Swift 1.5 Qwen3.8-Flash-Next
- Cola2 vs ThinkingCap (Qwen3.8 27B)
- Cola2 vs Baidu Unlimited-OCR-2
- Cola2 vs WeVisOne-VL-2B
- Cola2 vs WeVisOne-VL-4B
- Cola2 vs ZAYA1-8B
- Cosmos-Reason2-2B vs Hy-Memory-30B-A3B
- Darwin-36B-Opus vs Hy-Memory-30B-A3B
- DeepSeek-V3.2 vs Hy-Memory-30B-A3B
- DeepSeek V4.1 Flash vs Hy-Memory-30B-A3B
- DeepSeek-V4-Flash-0731 vs Hy-Memory-30B-A3B
- Devstral Small 2 vs Hy-Memory-30B-A3B
- DiffusionGemma 26B A4B IT vs Hy-Memory-30B-A3B
- EXAONE 4.5 33B vs Hy-Memory-30B-A3B
- Gemma 4 12B IT vs Hy-Memory-30B-A3B
- Gemma 4 26B A4B IT vs Hy-Memory-30B-A3B
- Gemma 4 31B IT vs Hy-Memory-30B-A3B
- Gemma 4 E2B IT vs Hy-Memory-30B-A3B
- Gemma 4 E4B IT vs Hy-Memory-30B-A3B
- GLM-4.5-Air vs Hy-Memory-30B-A3B
- GLM-4.7-Flash vs Hy-Memory-30B-A3B
- GLM-5.3-Flash vs Hy-Memory-30B-A3B
- GLM-5.3 vs Hy-Memory-30B-A3B
- gpt-oss-120b vs Hy-Memory-30B-A3B
- gpt-oss-20b vs Hy-Memory-30B-A3B
- Granite 4.2 30B vs Hy-Memory-30B-A3B
- Granite 4.2 3B vs Hy-Memory-30B-A3B
- Granite 4.2 8B vs Hy-Memory-30B-A3B
- Hy-Memory-30B-A3B vs Hy3
- Hy-Memory-30B-A3B vs Inkling
- Hy-Memory-30B-A3B vs Inkling-Small
- Hy-Memory-30B-A3B vs InternVL3.5-GPT-OSS-20B-A4B-Preview
- Hy-Memory-30B-A3B vs Kimi K3
- Hy-Memory-30B-A3B vs Kimi K3.1 Pro
- Hy-Memory-30B-A3B vs Kolibri-1
- Hy-Memory-30B-A3B vs Kronos
- Hy-Memory-30B-A3B vs Laguna M.1
- Hy-Memory-30B-A3B vs Laguna S 2.1
- Hy-Memory-30B-A3B vs Laguna XS 2.1
- Hy-Memory-30B-A3B vs LBS-27B
- Hy-Memory-30B-A3B vs LFM2.5-2.6B
- Hy-Memory-30B-A3B vs LFM3-1.7B
- Hy-Memory-30B-A3B vs LFM3-Audio-2B
- Hy-Memory-30B-A3B vs LFM3-Omni-2B
- Hy-Memory-30B-A3B vs LFM3-VL-2B
- Hy-Memory-30B-A3B vs Ling-3.0-tiny
- Hy-Memory-30B-A3B vs Ling-3.1-flash-1019
- Hy-Memory-30B-A3B vs LongCat-2.5
- Hy-Memory-30B-A3B vs MiMo-V2.6 Distill Qwen 9B
- Hy-Memory-30B-A3B vs MiMo-V2.6-Flash-RL
- Hy-Memory-30B-A3B vs MiniCPM-o 4.5
- Hy-Memory-30B-A3B vs MiniCPM-V 4.7 1B
- Hy-Memory-30B-A3B vs MiniCPM-V 4.7 35B-A3B
- Hy-Memory-30B-A3B vs MiniCPM5-2B
- Hy-Memory-30B-A3B vs MiniMax-M2.5
- Hy-Memory-30B-A3B vs MiniMax-M2.7
- Hy-Memory-30B-A3B vs MiniMax-M3.1-Flash
- Hy-Memory-30B-A3B vs Mistral Large 4
- Hy-Memory-30B-A3B vs Muse Glimmer 30B
- Hy-Memory-30B-A3B vs Nanbeige4.2-3B
- Hy-Memory-30B-A3B vs Nanbeige4.3-33B
- Hy-Memory-30B-A3B vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- Hy-Memory-30B-A3B vs Nemotron 3.5 Lightning 30B A3B
- Hy-Memory-30B-A3B vs Nemotron 3 Nano 30B A3B
- Hy-Memory-30B-A3B vs Nemotron 3 Nano 4B
- Hy-Memory-30B-A3B vs Nemotron 3 Nano Omni 30B A3B Reasoning
- Hy-Memory-30B-A3B vs Nemotron 3 Super 120B A12B
- Hy-Memory-30B-A3B vs Nemotron 3 Ultra 550B A55B
- Hy-Memory-30B-A3B vs North Mini Code 1.0
- Hy-Memory-30B-A3B vs occamy-1.0
- Hy-Memory-30B-A3B vs Olmo 3 7B Think
- Hy-Memory-30B-A3B vs Ornith-1.5-122B
- Hy-Memory-30B-A3B vs Ornith-1.5-35B-A3B
- Hy-Memory-30B-A3B vs Ornith-1.5-397B
- Hy-Memory-30B-A3B vs Ornith-1.5-9B
- Hy-Memory-30B-A3B vs OTel-2.0-LLM-31B-IT
- Hy-Memory-30B-A3B vs Qwen-AgentWorld-35B-A3B
- Hy-Memory-30B-A3B vs Qwen3-30B-A3B-Instruct-2507
- Hy-Memory-30B-A3B vs Qwen3-4B-Instruct-2507
- Hy-Memory-30B-A3B vs Qwen3.5-0.8B
- Hy-Memory-30B-A3B vs Qwen3.5-122B-A10B
- Hy-Memory-30B-A3B vs Qwen3.5-2B
- Hy-Memory-30B-A3B vs Qwen3.5-397B-A17B
- Hy-Memory-30B-A3B vs Qwen3.5-4B
- Hy-Memory-30B-A3B vs Qwen3.5-9B
- Hy-Memory-30B-A3B vs Qwen3.6-27B
- Hy-Memory-30B-A3B vs Qwen3.6-35B-A3B
- Hy-Memory-30B-A3B vs Qwen3.8-27B
- Hy-Memory-30B-A3B vs Qwen3.8-Flash-Next
- Hy-Memory-30B-A3B vs Qwen3-Coder-30B-A3B-Instruct
- Hy-Memory-30B-A3B vs Qwen3-Coder-Next
- Hy-Memory-30B-A3B vs Qwen3-Omni-30B-A3B-Instruct
- Hy-Memory-30B-A3B vs Qwen3-VL-2B-Instruct
- Hy-Memory-30B-A3B vs Qwen3-VL-30B-A3B-Instruct
- Hy-Memory-30B-A3B vs Qwen3-VL-32B-Instruct
- Hy-Memory-30B-A3B vs Qwen3-VL-4B-Instruct
- Hy-Memory-30B-A3B vs Qwen3-VL-8B-Instruct
- Hy-Memory-30B-A3B vs Qwopus3.8-27B-Flash-V2
- Hy-Memory-30B-A3B vs Recursive Flint
- Hy-Memory-30B-A3B vs Ripple-65B Preview
- Hy-Memory-30B-A3B vs SenseNova-Loop-9B-Preview
- Hy-Memory-30B-A3B vs SmolLM3-3B
- Hy-Memory-30B-A3B vs Spark-X2.6-4B
- Hy-Memory-30B-A3B vs Step 3.7 Flash
- Hy-Memory-30B-A3B vs Swift 1.5 Qwen3.8-27B
- Hy-Memory-30B-A3B vs Swift 1.5 Qwen3.8-Flash-Next
- Hy-Memory-30B-A3B vs ThinkingCap (Qwen3.8 27B)
- Hy-Memory-30B-A3B vs Baidu Unlimited-OCR-2
- Hy-Memory-30B-A3B vs WeVisOne-VL-2B
- Hy-Memory-30B-A3B vs WeVisOne-VL-4B
- Hy-Memory-30B-A3B vs ZAYA1-8B
Machine-readable
- This page as Markdown
/compare/cola2-vs-hy-memory-30b-a3b.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/cola2.json·/api/v1/tools/hy-memory-30b-a3b.json - From a terminal
anchor compare cola2 hy-memory-30b-a3b(the CLI) - Over MCP
compare_tools {"a": "cola2", "b": "hy-memory-30b-a3b"}at/mcp, no key