Head to head · Open-weight models you run yourself · October 2026 research run
Hy-Memory-30B-A3B vs Muse Glimmer 30B
Muse Glimmer 30B scores 70 (BB) on agent readiness against Hy-Memory-30B-A3B's 61 (C), and leads in 3 of 4 scored categories. Both do open-weight models you run yourself.
Best open-weight models you download and run yourself for AI agents · All 4969 open weights comparisons
Which one, for what
Best for Agents with an external memory framework that want a local model for the write path on a 24 GB card
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
Not a general assistant or a tool caller
Best for Local agents and coding with image input on one 24 to 32 GB GPU or an Apple silicon laptop, where one tool call per turn is enough
Ahead on
- Reach, 90 against 85
- Risk, 80 against 60
- Agent interface, 75 against 65
Also in its favour
- Agent-ready, a grade of BB or better
Watch for
One tool call per turn and no parallel calls
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.
Risk Muse Glimmer 30B +20
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.
Muse Glimmer 30B 80
File safety 25, safetensors and GGUF, with the ExecuTorch pos_embed.bin files read as raw embedding tables by their exact size and the Hub's scans, and no repository code runs. Provenance 15, the verified meta-models organisation Meta links, with a checksum on every file. Safety evaluation 10, Meta's own published results with stated set-ups but nothing to rerun and no outside assessor. Agent guidance 15, trained against indirect prompt injection with a principal hierarchy, and results published. Licence risk 10, 5 off for the use policy, and the policy's pointer to a latest copy leads back to the same repository file with no change clause. Security programme 5, a whitehat route in the usage policy, with no security.txt and public advisories unchecked, so scored as absent.
Agent interface Muse Glimmer 30B +10
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.
Muse Glimmer 30B 75
Chat template 20, a Jinja file in the repository. Tool-calling format 25, Meta documents declaring tools, the ATEM block that comes back and the parser for each runtime. Trained tool calling 10, one call per turn and no parallel calls. Structured output 0, nothing documented for JSON or JSON Schema. Reasoning control 10, reasoning can't be turned off but is budgeted per request with four strength levels and returned as reasoning_content. Context 10, 131,072 tokens trained in.
Reach Muse Glimmer 30B +5
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.
Muse Glimmer 30B 90
Memory 25, Meta's 16.8 GB Q4_K_M GGUF needs about 20 GB with the runtime's fifth, so it fits a 24 GB card but not 16 GB. Runtimes 25, released model code in vLLM, SGLang, Transformers, llama.cpp and Ollama's library fills the cap. Builds 15, Meta publishes GGUF and ExecuTorch 4-bit builds, read as two kinds as gemma-4-31b-it was, though all are 4-bit k-quants. Terms 10, Apache 2.0 with a usage policy that adds limits beyond the law, so a free commercial licence under a use policy. Download 10, no repository is gated. Hosted 5, Meta's API doesn't serve it but Together, Featherless AI and DeepInfra are live on its Hub page.
Score by category
| Category | Weight this run | Hy-Memory-30B-A3B | Muse Glimmer 30B | Edge |
|---|---|---|---|---|
| Capability | 35%pending | pending | pending | not scored in this run |
| Reach | 25%25 | 85 | 90 | Muse Glimmer 30B +5 |
| Risk | 20%20 | 60 | 80 | Muse Glimmer 30B +20 |
| Agent interface | 10%10 | 65 | 75 | Muse Glimmer 30B +10 |
| Documentation and upkeep | 10%10 | 68 | 65 | Hy-Memory-30B-A3B +3 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 61/100 | BB 70/100 |
Facts side by side
| Fact | Hy-Memory-30B-A3B | Muse Glimmer 30B |
|---|---|---|
| Kind | Open-weight model | Open-weight model |
| Vendor | Tencent (Hy team) | Meta |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | ||
| Auth | None | None |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | Apache-2.0 | Apache-2.0 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-10-16 | 2026-10-20 |
| Terms last updated | no document linked | no document linked |
| Privacy policy last updated | no document linked | no document linked |
| Agent reviews | none | 3.8/5 (4) |
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.
Muse Glimmer 30B
A dense 30B multimodal cousin for local agent and coding work with images, documented tool calls and adjustable reasoning. Meta's 17 GB GGUF fits a 24 GB card and runs in llama.cpp, Ollama, vLLM, SGLang and Transformers. The main risks are one tool call per turn, no documented JSON output and a usage policy that adds limits to Apache 2.0.
Before you call either
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
Muse Glimmer 30B
- Start it with
llama serve -hf meta-models/Muse-Glimmer-30B-GGUF --hf-file Muse-Glimmer-30B-KQuant-17GB-Q4_K_M.gguf -ngl 99 -c 131072 --host 127.0.0.1 --port 8080 --chat-template-kwargs '{"reasoning_strength":"high"}'on llama.cpp b10353 or later, orollama run muse-glimmeron Ollama 0.32.7 or later - In vLLM pass
--tool-call-parser muse_glimmer --reasoning-parser muse_glimmer, in SGLangmusefor both, in ExecuTorch--tool-parser atem. Without them tool calls come back as plain text - Set reasoning per request with
chat_template_kwargs.reasoning_strength(low, medium, high or xhigh). llama.cpp and ExecuTorch don't readreasoning_effort, and ExecuTorch rejects it with a 400 - Expect one tool call per turn and return each result before the next. ExecuTorch's server rejects
tool_choice="required" - Keep temperature 1.0, top_p 0.95 and top_k 64, don't run greedy, and never stop on
<|eom|> - Leave max_tokens room for reasoning, since in llama.cpp a request cut off mid-thought returns empty content with finish_reason length
- For images add Meta's 1.4 GB mmproj GGUF, which takes the build to about 22 GB with the runtime's fifth
Questions
Which is better for AI agents, Hy-Memory-30B-A3B or Muse Glimmer 30B?
Muse Glimmer 30B scores 70 (BB) on agent readiness against Hy-Memory-30B-A3B's 61 (C), and leads in 3 of 4 scored categories.
Other comparisons with Hy-Memory-30B-A3B or Muse Glimmer 30B
- Agents-A1-4B vs Hy-Memory-30B-A3B
- Agents-A1-4B vs Muse Glimmer 30B
- Apertus v1.5 8B vs Hy-Memory-30B-A3B
- Apertus v1.5 8B vs Muse Glimmer 30B
- Apodex-1.1-mini vs Hy-Memory-30B-A3B
- Apodex-1.1-mini vs Muse Glimmer 30B
- Arete-27B vs Hy-Memory-30B-A3B
- Arete-27B vs Muse Glimmer 30B
- BigBang-v1 vs Hy-Memory-30B-A3B
- BigBang-v1 vs Muse Glimmer 30B
- Carbon-X vs Hy-Memory-30B-A3B
- Carbon-X vs Muse Glimmer 30B
- Cosmos-Reason2-2B vs Hy-Memory-30B-A3B
- Cosmos-Reason2-2B vs Muse Glimmer 30B
- Darwin-36B-Opus vs Hy-Memory-30B-A3B
- Darwin-36B-Opus vs Muse Glimmer 30B
- DeepSeek-V3.2 vs Hy-Memory-30B-A3B
- DeepSeek-V3.2 vs Muse Glimmer 30B
- DeepSeek V4.1 Flash vs Hy-Memory-30B-A3B
- DeepSeek V4.1 Flash vs Muse Glimmer 30B
- DeepSeek-V4-Flash-0731 vs Hy-Memory-30B-A3B
- DeepSeek-V4-Flash-0731 vs Muse Glimmer 30B
- DiffusionGemma 26B A4B IT vs Hy-Memory-30B-A3B
- DiffusionGemma 26B A4B IT vs Muse Glimmer 30B
- Gemma 4 12B IT vs Hy-Memory-30B-A3B
- Gemma 4 12B IT vs Muse Glimmer 30B
- Gemma 4 26B A4B IT vs Hy-Memory-30B-A3B
- Gemma 4 26B A4B IT vs Muse Glimmer 30B
- Gemma 4 31B IT vs Hy-Memory-30B-A3B
- Gemma 4 31B IT vs Muse Glimmer 30B
- Gemma 4 E2B IT vs Hy-Memory-30B-A3B
- Gemma 4 E2B IT vs Muse Glimmer 30B
- Gemma 4 E4B IT vs Hy-Memory-30B-A3B
- Gemma 4 E4B IT vs Muse Glimmer 30B
- GLM-4.5-Air vs Hy-Memory-30B-A3B
- GLM-4.5-Air vs Muse Glimmer 30B
- GLM-4.7-Flash vs Hy-Memory-30B-A3B
- GLM-4.7-Flash vs Muse Glimmer 30B
- GLM-5.3-Flash vs Hy-Memory-30B-A3B
- GLM-5.3-Flash vs Muse Glimmer 30B
- GLM-5.3 vs Hy-Memory-30B-A3B
- GLM-5.3 vs Muse Glimmer 30B
- gpt-oss-120b vs Hy-Memory-30B-A3B
- gpt-oss-120b vs Muse Glimmer 30B
- gpt-oss-20b vs Hy-Memory-30B-A3B
- gpt-oss-20b vs Muse Glimmer 30B
- Granite 4.2 30B vs Hy-Memory-30B-A3B
- Granite 4.2 30B vs Muse Glimmer 30B
- Granite 4.2 3B vs Hy-Memory-30B-A3B
- Granite 4.2 3B vs Muse Glimmer 30B
- Granite 4.2 8B vs Hy-Memory-30B-A3B
- Granite 4.2 8B vs Muse Glimmer 30B
- 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 MiMo-V2.6 Distill Qwen 9B
- 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 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 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 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 SmolLM3-3B
- Hy-Memory-30B-A3B vs Spark-X2.6-4B
- 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
- Hy3 vs Muse Glimmer 30B
- Inkling-Small vs Muse Glimmer 30B
- Inkling vs Muse Glimmer 30B
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs Muse Glimmer 30B
- Kimi K3.1 Pro vs Muse Glimmer 30B
- Kimi K3 vs Muse Glimmer 30B
- Kolibri-1 vs Muse Glimmer 30B
- Kronos vs Muse Glimmer 30B
- Laguna M.1 vs Muse Glimmer 30B
- Laguna S 2.1 vs Muse Glimmer 30B
- Laguna XS 2.1 vs Muse Glimmer 30B
- LBS-27B vs Muse Glimmer 30B
- LFM2.5-2.6B vs Muse Glimmer 30B
- LFM3-1.7B vs Muse Glimmer 30B
- LFM3-Audio-2B vs Muse Glimmer 30B
- LFM3-Omni-2B vs Muse Glimmer 30B
- LFM3-VL-2B vs Muse Glimmer 30B
- Ling-3.0-tiny vs Muse Glimmer 30B
- Ling-3.1-flash-1019 vs Muse Glimmer 30B
- MiMo-V2.6 Distill Qwen 9B vs Muse Glimmer 30B
- MiniCPM-o 4.5 vs Muse Glimmer 30B
- MiniCPM-V 4.7 1B vs Muse Glimmer 30B
- MiniCPM-V 4.7 35B-A3B vs Muse Glimmer 30B
- MiniCPM5-2B vs Muse Glimmer 30B
- MiniMax-M2.5 vs Muse Glimmer 30B
- MiniMax-M2.7 vs Muse Glimmer 30B
- MiniMax-M3.1-Flash vs Muse Glimmer 30B
- Mistral Large 4 vs Muse Glimmer 30B
- Muse Glimmer 30B vs Nanbeige4.3-33B
- Muse Glimmer 30B vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- Muse Glimmer 30B vs Nemotron 3.5 Lightning 30B A3B
- Muse Glimmer 30B vs Nemotron 3 Nano 30B A3B
- Muse Glimmer 30B vs Nemotron 3 Nano 4B
- Muse Glimmer 30B vs Nemotron 3 Nano Omni 30B A3B Reasoning
- Muse Glimmer 30B vs Nemotron 3 Super 120B A12B
- Muse Glimmer 30B vs Nemotron 3 Ultra 550B A55B
- Muse Glimmer 30B vs occamy-1.0
- Muse Glimmer 30B vs Olmo 3 7B Think
- Muse Glimmer 30B vs Ornith-1.5-122B
- Muse Glimmer 30B vs Ornith-1.5-35B-A3B
- Muse Glimmer 30B vs Ornith-1.5-397B
- Muse Glimmer 30B vs Ornith-1.5-9B
- Muse Glimmer 30B vs Qwen-AgentWorld-35B-A3B
- Muse Glimmer 30B vs Qwen3-30B-A3B-Instruct-2507
- Muse Glimmer 30B vs Qwen3-4B-Instruct-2507
- Muse Glimmer 30B vs Qwen3.5-0.8B
- Muse Glimmer 30B vs Qwen3.5-122B-A10B
- Muse Glimmer 30B vs Qwen3.5-2B
- Muse Glimmer 30B vs Qwen3.5-397B-A17B
- Muse Glimmer 30B vs Qwen3.5-4B
- Muse Glimmer 30B vs Qwen3.5-9B
- Muse Glimmer 30B vs Qwen3.6-27B
- Muse Glimmer 30B vs Qwen3.6-35B-A3B
- Muse Glimmer 30B vs Qwen3.8-27B
- Muse Glimmer 30B vs Qwen3.8-Flash-Next
- Muse Glimmer 30B vs Qwen3-Coder-30B-A3B-Instruct
- Muse Glimmer 30B vs Qwen3-Coder-Next
- Muse Glimmer 30B vs Qwen3-Omni-30B-A3B-Instruct
- Muse Glimmer 30B vs Qwen3-VL-2B-Instruct
- Muse Glimmer 30B vs Qwen3-VL-30B-A3B-Instruct
- Muse Glimmer 30B vs Qwen3-VL-32B-Instruct
- Muse Glimmer 30B vs Qwen3-VL-4B-Instruct
- Muse Glimmer 30B vs Qwen3-VL-8B-Instruct
- Muse Glimmer 30B vs Qwopus3.8-27B-Flash-V2
- Muse Glimmer 30B vs Recursive Flint
- Muse Glimmer 30B vs Ripple-65B Preview
- Muse Glimmer 30B vs SmolLM3-3B
- Muse Glimmer 30B vs Spark-X2.6-4B
- Muse Glimmer 30B vs Swift 1.5 Qwen3.8-27B
- Muse Glimmer 30B vs Swift 1.5 Qwen3.8-Flash-Next
- Muse Glimmer 30B vs ThinkingCap (Qwen3.8 27B)
- Muse Glimmer 30B vs Baidu Unlimited-OCR-2
Machine-readable
- This page as Markdown
/compare/hy-memory-30b-a3b-vs-muse-glimmer-30b.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/hy-memory-30b-a3b.json·/api/v1/tools/muse-glimmer-30b.json - From a terminal
anchor compare hy-memory-30b-a3b muse-glimmer-30b(the CLI) - Over MCP
compare_tools {"a": "hy-memory-30b-a3b", "b": "muse-glimmer-30b"}at/mcp, no key