
Real head-to-head · same prompt, one shot
Hy3 vs Kimi K2.7 · No-Think
Tencent's open-weights coder — Apache-2.0, cheap, beats GLM-5.1 on frontend in Tencent's blind eval. vs Pure execution mode — no chain of thought.
What I tested — same prompt, two models
I run the same fixed prompt set through every new model the day it drops — same string, one shot, single HTML file out — and I score the result 0–10 on whether it ran, how close it hit the brief, and how good it looked. Below is what came out when I gave the exact same prompts to Hy3 and Kimi K2.7 · No-Think, side by side, on 7 shared tasks inside the Agent Operating System.
Both models were given identical prompts inside the Agent Operating System — no help, no iteration, no "best of N" tricks. I run each prompt once, save the HTML file the model produces, and score it 0–10 on whether it ran, how close it hit the brief, and how good it looked. The scoring is mine. The verdicts below are pulled from my source comparison guides at agentos.guide where I publish every score and the reasoning behind it.
Hy3 · Wired into the Agent OS as the 'Hy3 Coder' tab (chat + live preview + workspace) via OpenRouter. Bench built one-shot on the same prompts as the field; weak builds iterated by Hy3 itself (the model fixes its own builds).
Kimi K2.7 · No-Think · Reserved for templated transforms where the plan is already in the prompt — the model just executes.
Side-by-side on 47 shared tasks
Click any cell to play that model's actual one-shot attempt. Medals are derived from my 0–10 scores per task (highest = 🥇, second = 🥈, third = 🥉).
Task ↓
Hy3
Kimi K2.7 · No-Think
Game
Game
Game
Game
Game
Game
Page
Game
— not attempted —
Game
— not attempted —
Game
— not attempted —
Game
— not attempted —
Game
— not attempted —
Game
— not attempted —
Game
— not attempted —
Game
— not attempted —
Game
— not attempted —
Game
— not attempted —
Game
— not attempted —
Game
— not attempted —
Game
— not attempted —
Game
— not attempted —
Game
— not attempted —
Game
— not attempted —
Game
— not attempted —
Strengths & weaknesses I logged
Hy3
Strengths
- Apache-2.0 open weights — self-host free, no lock-in
- Tencent's 270-expert blind eval: 2.67/4 vs GLM-5.1's 2.51, strongest on frontend / data / CI-CD
- Hallucination rate cut 12.5% → 5.4%; stable tool-calls across scaffoldings (<4% SWE-Bench variance)
Trade-offs
- Slow upstream on OpenRouter (30-90s per build) — fine for one-shots, sluggish for tight loops
- One-shot game builds can under-render (flat raycaster walls, unlit 3D) without an iterate pass
Kimi K2.7 · No-Think
Strengths
- Skips planning to ship straight to code
- Useful when you've already done the reasoning in the prompt
- Predictable latency for batched jobs
Trade-offs
- Loses ground on multi-step tasks that benefit from planning
- Not scored on the standalone bench — see methodology
Pricing & context — the spec sheet
| Spec | Hy3 | Kimi K2.7 · No-Think |
|---|---|---|
| Vendor | Tencent Hunyuan | Moonshot AI |
| Context window | 262,144-token context window. Open weights (Apache-2.0) on HuggingFace / ModelScope / GitHub; benched here via OpenRouter. | 256,000 tokens |
| Price | $0.14 / 1M input · $0.58 / 1M output | Flat plan (no per-token bill) |
| Pricing detail | Tencent Hunyuan 3 — open-weights under Apache-2.0, so free to self-host. On OpenRouter it is one of the cheapest capable coders: ~$0.14/M in, $0.58/M out (1 RMB / 4 RMB). Upstream can be slow (30-90s to first token), but per-token cost is negligible. | Same flat-rate plan as standard Kimi K2.7 — No-Think disables the chain-of-thought layer at runtime. Vendor: Moonshot AI (moonshot.ai). |
| Release | 2026-07-06 | 2026-06 |
| Bench coverage | 7/7 scored · avg 7.13/10 | 0/47 scored · avg — |
The verdict — which should you pick?
Not enough scored shared tasks yet for a head-to-head average. The live demos for both are on the matrix above — play them and form your own opinion.
If you only run one of these inside your stack, the head-to-head average above is the call. If you can run both, my honest play is to wire Hy3 and Kimi K2.7 · No-Think both into the Agent Operating System and dispatch each from the kanban by task type — cost-sensitive coding + frontend design where open weights matter → Hy3, templated transforms where the plan is in the prompt → Kimi K2.7 · No-Think. That's the same setup I run for the 3,600+ founders inside the AI Profit Boardroom.
FAQ — Hy3 vs Kimi K2.7 · No-Think
Which is better, Hy3 or Kimi K2.7 · No-Think?
On Goldie Bench, Hy3 averages no scored verdicts yet across the shared tasks, with 0 gold, 1 silver, 0 bronze overall. Kimi K2.7 · No-Think averages no scored verdicts yet, with 0 gold, 0 silver, 0 bronze. Not enough scored shared tasks yet to call a winner.
How much does Hy3 cost vs Kimi K2.7 · No-Think?
Hy3: Tencent Hunyuan 3 — open-weights under Apache-2.0, so free to self-host. On OpenRouter it is one of the cheapest capable coders: ~$0.14/M in, $0.58/M out (1 RMB / 4 RMB). Upstream can be slow (30-90s to first token), but per-token cost is negligible. Kimi K2.7 · No-Think: Same flat-rate plan as standard Kimi K2.7 — No-Think disables the chain-of-thought layer at runtime. Vendor: Moonshot AI (moonshot.ai).
What's the context window for Hy3 vs Kimi K2.7 · No-Think?
Hy3 has a 262,144-token context window. Open weights (Apache-2.0) on HuggingFace / ModelScope / GitHub; benched here via OpenRouter. context window. Kimi K2.7 · No-Think has a 256,000 tokens context window.
When should I pick Hy3 over Kimi K2.7 · No-Think?
Pick Hy3 for: Cost-sensitive coding + frontend design where open weights matter; Self-hosters who want an Apache-2.0 model they fully own; Anyone wiring a cheap capable coder into a live build panel (Agent OS Hy3 Coder tab). The trade-off is the weaknesses we logged on the bench: Slow upstream on OpenRouter (30-90s per build) — fine for one-shots, sluggish for tight loops; One-shot game builds can under-render (flat raycaster walls, unlit 3D) without an iterate pass.
When should I pick Kimi K2.7 · No-Think over Hy3?
Pick Kimi K2.7 · No-Think for: Templated transforms where the plan is in the prompt; Batched code generation jobs; Workflows where you want the model to stop second-guessing. The trade-off is the weaknesses we logged on the bench: Loses ground on multi-step tasks that benefit from planning; Not scored on the standalone bench — see methodology.
How does Goldie Bench score Hy3 vs Kimi K2.7 · No-Think?
Every demo on this page was built by Julian Goldie inside the Agent Operating System — same fixed prompt for both models, one shot, single HTML file out. Each result gets a 0–10 score on whether it ran, how close it hit the brief, and how good it looked. The highest score on each task gets gold; second gets silver; third gets bronze. See methodology for full provenance.
Related comparisons
Other head-to-heads using the same scoring system:
Hy3 vs Fusion Kimi K2.7 · No-Think vs Fusion Hy3 vs Hermes MoA Kimi K2.7 · No-Think vs Hermes MoA Hy3 vs Claude Fable 5 Kimi K2.7 · No-Think vs Claude Fable 5 Hy3 vs Grok Kimi K2.7 · No-Think vs GrokFull model pages: Hy3 · Kimi K2.7 · No-Think · back to the leaderboard
The same stack Julian uses
Run this stack yourself.
Every demo on this bench was built inside the Agent Operating System — one prompt, one shot, single HTML file out. The Agent OS, the prompts, the templates, the weekly walkthroughs and 3,600+ founders shipping with it every day all live inside the AI Profit Boardroom.
3,600+founders
258documented wins
38countries
$59/momonthly





























