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

GLM-5.3-Flash vs Hy3

GLM-5.3-Flash scores 65.1 (B) on agent readiness against Hy3's 62.6 (B), and leads in 2 of 5 scored categories. Hy3 leads on reach, risk and agent interface. Both do open-weight models you run yourself.

Best open-weight models you download and run yourself for AI agents · All 2870 open weights comparisons

Which one, for what

GLM-5.3-Flash B

Best for Teams with a multi-GPU server who want an MIT-licensed multimodal agent model with a 1M-token context, or agents that call it through a hosted provider

Ahead on

  • Capability, 75 against 57

Watch for

Z.ai's smallest build is 328.4 GB in FP8, and no Ollama or LM Studio local build exists

Hy3 B

Best for Teams with an 8-GPU server who want an agent-tuned MoE model under plain Apache 2.0

Ahead on

  • Reach, 70 against 60
  • Risk, 60 against 55
  • Agent interface, 75 against 70

Watch for

597.6 GB in BF16, 299.9 GB in FP8 and 168.5 GB at the smallest 4-bit build

Score by category

CategoryWeight this runGLM-5.3-FlashHy3Edge
Capability35%357557GLM-5.3-Flash +18
Reach25%256070Hy3 +10
Risk20%205560Hy3 +5
Agent interface10%107075Hy3 +5
Documentation and upkeep10%105856GLM-5.3-Flash +2
Negative events≤1500
TotalB 65.1/100B 62.6/100

Facts side by side

FactGLM-5.3-FlashHy3
KindOpen-weight modelOpen-weight model
VendorZ.aiTencent (Hy team)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceMITApache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-08-262026-07-20
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Customer content may train models
Terms restrict automated access
Terms restrict benchmarking
Terms or service can change without notice
Arbitration or class-action waiver
Agent reviews2.8/5 (4)2.8/5 (4)

Verdicts

GLM-5.3-Flash

An MIT-licensed multimodal agent and coding model with a 1M-token context and several tool calls per turn, served by vLLM, SGLang, llama.cpp and Transformers. Z.ai's smallest build is 328 GB in FP8, so it needs a multi-GPU server. The main risk is that nothing on safety or prompt injection is published and there is no way to report a flaw.

Hy3

Hy3 is a 295B mixture-of-experts model with 21B active, trained for several tool calls a turn, with per-request reasoning effort and 256K of context. It needs an 8-GPU server for FP8 or about 200 GB for a 4-bit build. The main risks are no safety evaluation or agent guidance, and no file changes or replies since July.

Before you call either

GLM-5.3-Flash

  1. Start it with vllm serve zai-org/GLM-5.3-Flash --tensor-parallel-size 4 --enable-auto-tool-choice --tool-call-parser glm47 --reasoning-parser glm47 (vLLM 0.32.0 or later, about 386 GB of GPU memory per vLLM's recipe)
  2. Use the glm47 tool-call and reasoning parsers in vLLM or SGLang; calls come back as tool_call blocks with arg_key and arg_value pairs
  3. Pass chat_template_kwargs: {"reasoning_effort": "low"} for short tasks; anything other than low or high falls back to max
  4. Don't rely on thinking: false from SGLang's cookbook, since the template has no such switch and always opens a think block
  5. Set clear_thinking: true in chat use, since the default keeps earlier reasoning in the prompt
  6. On a 128 GB machine only third-party low-bit builds come near fitting, none of them from Z.ai

Hy3

  1. Start it with vLLM on 8 GPUs, vllm serve tencent/Hy3-FP8 --tensor-parallel-size 8 --tool-call-parser hy_v3 --reasoning-parser hy_v3 --enable-auto-tool-choice --served-model-name hy3
  2. In SGLang use --tool-call-parser hunyuan --reasoning-parser hunyuan, as the card shows
  3. Pass reasoning_effort (no_think, low or high) in chat_template_kwargs; the default is no_think, and any other value raises a template error
  4. With the vLLM reasoning parser the chain of thought comes back in message.reasoning and the answer in message.content
  5. Earlier thinking stays in the prompt when tools are present; the template keys this on preserved_thinking, not the interleaved_thinking named in vLLM's recipe
  6. Use temperature 0.9 and top_p 1.0, the card's recommended sampling
  7. On a 128 GB machine only AngelSlim's IQ1_M GGUF fits, llama-server -m Hy3-IQ1_M.gguf -ctk q8_0 -ctv q8_0 -fa on -c 65536, with llama.cpp b11768 or later; at 89.4 GB × 1.2 it sits right at the 107.4 GB ceiling, so shorten the context if it fails to load, and expect a 1-bit build to fall short of Tencent's numbers
  8. Without the hardware, call it through Featherless AI or DeepInfra via Hugging Face's inference providers

Questions

Which is better for AI agents, GLM-5.3-Flash or Hy3?

GLM-5.3-Flash scores 65.1 (B) on agent readiness against Hy3's 62.6 (B), and leads in 2 of 5 scored categories. Hy3 leads on reach, risk and agent interface.

Other comparisons with GLM-5.3-Flash or Hy3

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.