Kimi K2.7 vs Kimi K3

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 Kimi K2.7 and Kimi K3, side by side, on 47 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.

Kimi K2.7 · Wired into the Agent OS as the heavy-lifter for game/sim prototypes and Kanban-dispatched code work. Mode toggled per task: Quality for one-shot games, Fast for short bursts.

Kimi K3 · Wired into the Agent OS as the `kimi-k3` Hermes profile and a K3 speed-toggle in the Kimi Code tab — used for long unattended agent runs where a slow-but-right model beats a fast-but-forgetful one.

Where Kimi K2.7 beat Kimi K3

The tasks where I gave Kimi K2.7 a higher 0–10 score on the same prompt — with the actual commentary from my source guides.

Where Kimi K3 beat Kimi K2.7

The tasks where I gave Kimi K3 a higher 0–10 score on the same prompt — with the actual commentary from my source guides.

Strengths & weaknesses I logged

Pricing & context — the spec sheet

The verdict — which should you pick?

Across 25 scored shared tasks, Kimi K2.7 averaged 7.46/10, beating Kimi K3's 5.09/10 by 2.37 points. Pick Kimi K2.7 when the build has to ship on the first prompt and you can afford the trade-offs in the comparison below.

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 Kimi K2.7 and Kimi K3 both into the Agent Operating System and dispatch each from the kanban by task type — interactive game prototypes you want shippable on the first prompt → Kimi K2.7, long-horizon agent runs → Kimi K3. That's the same setup I run for the 4,000+ founders inside the AI Profit Boardroom.

FAQ — Kimi K2.7 vs Kimi K3

Which is better, Kimi K2.7 or Kimi K3?

On Goldie Bench, Kimi K2.7 averages 7.46/10 across the shared tasks, with 2 gold, 1 silver, 2 bronze overall. Kimi K3 averages 5.09/10, with 9 gold, 5 silver, 7 bronze. Kimi K2.7 wins the head-to-head 16–9.

How much does Kimi K2.7 cost vs Kimi K3?

Kimi K2.7: Available on Moonshot's flat-rate subscription plan — no per-token billing for individual builders. The plan covers all three speed modes (Fast, No-Think, Quality). Vendor: Moonshot AI (moonshot.ai), based in Beijing. Kimi K3: Launched July 16, 2026. 2.5T-param MoE. $3/M input on OpenRouter at launch; included at no extra cost in the Kimi coding plan (`k3` on the coding endpoint).

What's the context window for Kimi K2.7 vs Kimi K3?

Kimi K2.7 has a 256,000 tokens context window. Kimi K3 has a 1,048,576 tokens — a full codebase in working memory context window.

When should I pick Kimi K2.7 over Kimi K3?

Pick Kimi K2.7 for: Interactive game prototypes you want shippable on the first prompt; High-iteration agent loops where per-token cost would dominate; Long-context refactors using the 256K window inside Agent OS. The trade-off is the weaknesses we logged on the bench: Plays plainest on abstract visual prompts — synthwave grids, fluid sims, aurora — where GLM and Opus add more flair; Bronze average on the {{SITE_NAME}} bench despite the gold-medal games — its visual builds are accurate but understated.

When should I pick Kimi K3 over Kimi K2.7?

Pick Kimi K3 for: long-horizon agent runs; whole-repo context work; terminal-driving agents. The trade-off is the weaknesses we logged on the bench: Slow on hard tasks — early testers report up to ~35 minutes at max reasoning; this bench saw 13+ minute single builds; Launch-day rate limits on OpenRouter (429s) — the coding-plan endpoint was the reliable route; Self-reports as K2.7 if you ask it — verify the served model via the API response, not the model's word.

How does Goldie Bench score Kimi K2.7 vs Kimi K3?

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:

Full model pages: Kimi K2.7 · Kimi K3 · back to the leaderboard