Kimi K3.1 Pro: China's Open-Weight Model Just Caught the Frontier

Moonshot AI released Kimi K3.1 Pro, a 3T-class open-weight model with a one-million-token context window, and the benchmark table attached to the announcement is the most consequential number in Chinese AI this month. On Terminal-Bench 4.0 — a test that grades coding agents on realistic, resource-constrained terminal work with strict task-specific checks — K3.1 Pro reports 65.7%. GPT-6 Astra sits at 58.2%. Claude Opus 5.5 sits at 66.4%.

That is a gap of seven-tenths of a point against the strongest proprietary model on the market, from a lab that promises to publish the full weights by November 4.

The honest reading is narrower than “China has caught up.” A 0.7-point deficit is within the range where prompt choice, harness configuration, and task sampling can flip the ordering. But the shape of the result matters more than the exact decimal: an open-weight model is now scoring in the same band as closed frontier systems on agentic coding work, not trailing by a generation.

What actually shipped

K3.1 Pro is described as a post-trained version of Kimi K3 with substantially larger post-training compute. Moonshot says it optimized the entire stack — RL framework, long-context inference, training efficiency, sandbox infrastructure, rollout scheduling, and a shared environment-quality platform — to make each increment of RL compute return stable gains. That is the least glamorous paragraph in the announcement and probably the most important one: the claim is not that a single clever trick produced the jump, but that the training pipeline stopped wasting compute.

A second variant, K3.1 Pro Highspeed, reports 2–3× the speed of the base model. Both are live now on Kimi.com, Kimi Work, Kimi Code, and the Kimi API.

On Moonshot’s internal Kimi Code Bench 3.0 Long-horizon — which tests multi-step execution, tool use, and end-to-end problem solving — the company reports 61.2% for K3.1 Pro versus 55.95% for K3. And the announcement claims gains across coding, 3D creation, financial research, and other agentic capabilities.

Every one of those numbers is vendor-reported. None has been independently reproduced at the time of writing.

The weight release is the real story

Terminal-Bench scores are interesting. The weight release schedule is the part that changes decisions.

A closed API at 66% forces a team into a build-vs-buy conversation shaped by pricing, rate limits, data residency, and deprecation risk. An open-weight model at 65.7% with a million-token context lets that team download the checkpoint, run it inside its own perimeter, fine-tune it on proprietary data, and keep working even if the vendor changes its pricing page.

For regulated industries — finance, healthcare, anything touching customer records that cannot leave a jurisdiction — that is not a marginal preference. It is often the only path that clears legal review.

The caveat is infrastructure. A 3T-class model is not a laptop download. Serving it needs real GPU capacity, and the economics only work at batch sizes and utilization levels that most small teams cannot sustain. The “open” in open-weight has always meant “open to those who can afford the hardware.”

Why the benchmark gap is smaller than it looks

Terminal-Bench 4.0 is a well-constructed test in that it grades outcomes, not vibes: a task either passes its checks or it does not. That makes it much harder to game than a preference-based leaderboard. It also means a 0.7-point difference is close to noise at typical sample sizes.

Three things move the number more than the model does. First, the agent harness — the loop that decides when to read a file, when to run a command, and when to stop. Second, the retry policy under failure. Third, whether the environment matches the one the model was trained against.

A team that ports its existing Claude harness to K3.1 Pro without tuning will not see 65.7%. It will see whatever its scaffolding produces, which may be meaningfully worse.

The practical takeaway

Kimi K3.1 Pro is the first open-weight model where “we can self-host and stay competitive on agentic coding” is a defensible sentence rather than an aspiration. The weights arrive November 4. Between now and then, the useful work is not re-running leaderboard benchmarks — it is running your own harness against the API on the tasks your team actually fails at.

If K3.1 Pro clears that bar, the strategic case for a closed-only stack weakens. If it does not, the Terminal-Bench headline will look like what it probably is: a real advance, measured on one axis, announced before independent replication.