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

GLM-4.7-Flash vs Hy3

GLM-4.7-Flash and Hy3 score within a point of each other on agent readiness, 63 (B) and 62.6 (B). Hy3 leads on risk and documentation and upkeep. 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-4.7-Flash B

Best for Agents and developers who want a small, permissively licensed tool-calling model on one 24 to 32 GB GPU or Mac, in almost any runtime

Ahead on

  • Reach, 80 against 70
  • Agent interface, 85 against 75

Watch for

No change to the files since 29 January 2026 and no zai-org reply on discussions since 31 January

Hy3 B

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

Ahead on

  • Risk, 60 against 55
  • Documentation and upkeep, 56 against 28

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-4.7-FlashHy3Edge
Capability35%355957GLM-4.7-Flash +2
Reach25%258070GLM-4.7-Flash +10
Risk20%205560Hy3 +5
Agent interface10%108575GLM-4.7-Flash +10
Documentation and upkeep10%102856Hy3 +28
Negative events≤1500
TotalB 63/100B 62.6/100

Facts side by side

FactGLM-4.7-FlashHy3
KindOpen-weight modelOpen-weight model
VendorZ.ai (Zhipu AI)Tencent (Hy team)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceMITApache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-01-292026-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-4.7-Flash

A small MIT-licensed mixture-of-experts model with about 3B active parameters, for local agent and coding work with several tool calls per turn and optional thinking. It runs in Ollama at about 23 GB and in nearly every common runtime. The main risk is neglect, with no changes or replies since early February and no safety results.

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-4.7-Flash

  1. On our reference machine start it with vllm serve zai-org/GLM-4.7-Flash --max-model-len 65536 --tool-call-parser glm47 --reasoning-parser glm45 --enable-auto-tool-choice --served-model-name glm-4.7-flash
  2. Or run ollama run glm-4.7-flash for the 19 GB q4_K_M build
  3. Without the glm47 and glm45 parsers, tool calls and reasoning come back as plain text
  4. Use a released vLLM (0.32.0 or later) or SGLang (0.5.22 or later); the card's nightly and pull-request builds date from January 2026
  5. Pass chat_template_kwargs: {"enable_thinking": false} for short tasks, since thinking is on by default
  6. Set clear_thinking: false to keep earlier reasoning in multi-turn agent work, as Z.ai does for τ²-Bench and Terminal Bench
  7. Set the context length yourself, since config.json allows 202,752 tokens and tokenizer_config.json says 128,000

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-4.7-Flash or Hy3?

GLM-4.7-Flash and Hy3 score within a point of each other on agent readiness, 63 (B) and 62.6 (B). Hy3 leads on risk and documentation and upkeep.

Other comparisons with GLM-4.7-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.