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

gpt-oss-120b vs Hy3

gpt-oss-120b scores 70.2 (BB) on agent readiness against Hy3's 62.6 (B), and leads in 3 of 5 scored categories. Hy3 leads on 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

gpt-oss-120b BB

Best for Agents on one 80 GB GPU or a 128 GB unified machine that want an Apache 2.0 reasoning model with wide runtime support

Ahead on

  • Reach, 75 against 70
  • Risk, 95 against 60
  • Agent interface, 90 against 75

Also in its favour

  • Agent-ready, a grade of BB or better
  • Rated higher by the reviewer agents, 3.5 against 2.8 out of 5

Watch for

Needs about 78 GB, too big for 64 GB machines, and OpenAI ships only one precision

Hy3 B

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

Ahead on

  • Documentation and upkeep, 56 against 45

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 rungpt-oss-120bHy3Edge
Capability35%355457Hy3 +3
Reach25%257570gpt-oss-120b +5
Risk20%209560gpt-oss-120b +35
Agent interface10%109075gpt-oss-120b +15
Documentation and upkeep10%104556Hy3 +11
Negative events≤1500
TotalBB 70.2/100B 62.6/100

Facts side by side

Factgpt-oss-120bHy3
KindOpen-weight modelOpen-weight model
VendorOpenAITencent (Hy team)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2025-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 reviews3.5/5 (4)2.8/5 (4)

Verdicts

gpt-oss-120b

A reasoning and agent cousin that runs in most runtimes under Apache 2.0 with published safety work. It needs about 78 GB of GPU memory, one 80 GB card or a 128 GB unified machine with the GPU limit raised. The main risks are tool calls one at a time and no replies to reports since August 2025.

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

gpt-oss-120b

  1. Start it with ollama run gpt-oss:120b on the reference machine, the build that fits
  2. On the Strix Halo machine raise the GPU memory limit first with amd-ttm --set 100, since the default of about 62.8 GiB is below the 78 GB it needs
  3. With vLLM use vllm serve openai/gpt-oss-120b --tool-call-parser openai --enable-auto-tool-choice per vLLM's recipe, or parse raw output with openai-harmony
  4. Always use the harmony format through the chat template or openai-harmony, the card says it won't work correctly otherwise
  5. Set Reasoning: low in the system message for short tasks, medium is the default
  6. Pass the reasoning back after a tool call until the final answer, and keep the analysis channel away from end users
  7. Expect one tool call per turn and loop, don't wait for parallel calls

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, gpt-oss-120b or Hy3?

gpt-oss-120b scores 70.2 (BB) on agent readiness against Hy3's 62.6 (B), and leads in 3 of 5 scored categories. Hy3 leads on documentation and upkeep.

Other comparisons with gpt-oss-120b 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.