Kimi K2.7 vs Gemini 3.6 Flash

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 Gemini 3.6 Flash, 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.

Gemini 3.6 Flash · Benched via the native Gemini API on launch day. Game tasks use the skill-infused threejs-game-director prompt (same as the rest of the field) and are judged on a real mid-play frame by the same Opus vision judge.

Where Kimi K2.7 beat Gemini 3.6 Flash

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 Gemini 3.6 Flash beat Kimi K2.7

The tasks where I gave Gemini 3.6 Flash 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, the averages are essentially tied — Kimi K2.7 7.46 vs Gemini 3.6 Flash 7.40. This isn't the comparison where one wins; it's the comparison where you pick based on context, pricing, and what you're actually trying to ship.

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 Gemini 3.6 Flash 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, high-volume agentic work where token cost dominates → Gemini 3.6 Flash. That's the same setup I run for the 4,000+ founders inside the AI Profit Boardroom.

FAQ — Kimi K2.7 vs Gemini 3.6 Flash

Which is better, Kimi K2.7 or Gemini 3.6 Flash?

On Goldie Bench, Kimi K2.7 averages 7.46/10 across the shared tasks, with 1 gold, 2 silver, 0 bronze overall. Gemini 3.6 Flash averages 7.40/10, with 2 gold, 3 silver, 2 bronze. Gemini 3.6 Flash wins the head-to-head 14–10.

How much does Kimi K2.7 cost vs Gemini 3.6 Flash?

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. Gemini 3.6 Flash: Launched 2026-07-21 alongside Gemini 3.5 Flash-Lite and 3.5 Flash Cyber. Google's pitch: higher intelligence than its predecessors on coding/ML/knowledge tasks while using 17% fewer output tokens, at a new lower price ($1.50 per million input tokens). Benched here via the native Gemini API on launch day.

What's the context window for Kimi K2.7 vs Gemini 3.6 Flash?

Kimi K2.7 has a 256,000 tokens context window. Gemini 3.6 Flash has a 1,000,000-token context window context window.

When should I pick Kimi K2.7 over Gemini 3.6 Flash?

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 Gemini 3.6 Flash over Kimi K2.7?

Pick Gemini 3.6 Flash for: High-volume agentic work where token cost dominates; Fast prototype builds you iterate on rather than one-shot masterpieces; Routing the everyday 90% while a flagship handles the hard 10%. The trade-off is the weaknesses we logged on the bench: Benched on launch day — partial run until the full 50-task batch completes; Flash tier, not a flagship — up against Pro/flagship-class models on this board.

How does Goldie Bench score Kimi K2.7 vs Gemini 3.6 Flash?

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 · Gemini 3.6 Flash · back to the leaderboard