activeCodingAgents

Kimi Code Bench v2

Metric: Score (higher is better)Introduced: 2026

Moonshot-reported proprietary coding benchmark for Kimi K2.7-Code launch comparisons. Keep separate from SWE-bench and Terminal-Bench public benchmark rows.

Models ranked

2

tracked on this benchmark

Score band

77.1 – 62.0

best → lowest tracked

Snapshot trend

+15.10

Jun 12 → Oct 23 · 1 models

Leaderboard

Tracked models ranked by Score (higher is better).

Compare candidates
#Model variant and provenanceScore
1
Version: Kimi Code Bench 2.0 (internal); Claude-Code harness; max reasoning effortHarness: Not recordedEvaluator: Not recordedObserved: Oct 23, 2026Confidence: Not recordedSource

Notes: Moonshot self-reported launch table, row 'Kimi Code Bench 2.0 (Internal)', column 'Kimi K3.1 Pro (max)'. Settings: reasoning effort max, temperature 1.0, top-p 0.95 (blog footnote). Moonshot internal benchmark.

77.1
2
Version: official, Moonshot-reportedHarness: Not recordedEvaluator: Not recordedObserved: Jun 12, 2026Confidence: Not recordedSource

Notes: Moonshot proprietary benchmark. Not comparable with SWE-bench or Terminal-Bench.

62.0

How to read this benchmark

This benchmark scores models where higher is better. Use scores for directional filtering and shortlisting, not universal quality ranking; then validate pricing, context window, provider availability, and fit for your workload.

Trust this score when

  • There is a fresh timestamped snapshot (or multiple snapshots) for this benchmark.
  • The model list covers the same version family you can actually deploy today.
  • Top candidates overlap with your required routing and feature requirements.

Be cautious when

  • There is only one benchmark snapshot or the dataset appears stale.
  • The benchmark metric direction is opposite of your decision objective.
  • The score difference between options is narrow and likely within implementation variance.

Related benchmarks

Last reviewed: Jun 19, 2026

Resources