BackgrindComparison
China's coding models, July 2026: who's actually good at what
July 2026 is the month the "Chinese models are catching up" story stopped being a prediction and became a scheduling problem: Moonshot, Qwen, Z.ai, and DeepSeek all shipped or updated agent-grade models within weeks of each other, and the strongest of them now sit within a few benchmark points of the US frontier — at a fraction of the price, often with weights you can download. If you run coding agents, this isn't geopolitics; it's a procurement question. Here's who's actually good at what, without the cheerleading.
The field, one axis at a time
The cleanest way to read the Chinese field right now is that each lab owns a different axis:
| Model | Owns the axis | What that means for agent work |
|---|---|---|
| GLM-5.2 (Z.ai) | Peak coding scores | Leads the Chinese field on independent coding and agent leaderboards — the "just give me the strongest one" pick. |
| Kimi K2.6 (Moonshot) | Long agent runs | The proven endurance pick: reported ~80.2 on SWE-Bench-class suites, and the reputation for staying coherent over long tool-calling sessions — the workload coding agents actually are. |
| Kimi K3 (Moonshot, July 16) | The new flagship bet | 2.8T-parameter MoE, 1M context, multimodal, $3/$15 pricing. Self-reported 81.2 FrontierSWE; independent evals still landing. Full breakdown in Fable 5 vs Kimi K3. |
| DeepSeek V4 | Price | The cost floor of the frontier-adjacent tier. When the task is high-volume grind — migrations, test scaffolds, batch edits — V4 does acceptable work for pennies. |
| Qwen3 Coder (Alibaba) | Open adoption | The most-adopted open base — the default weights people fine-tune and self-host. If "runs on my infra" is a requirement, start here. |
| Backgrind | Not a model — the overlay that runs whichever of these your CLI speaks, in tabs, with notifications. Model plurality is the point. | |
The honest caveats
- Self-reported vs independent. Launch-week numbers come from the labs. GLM-5.2's lead and K2.6's endurance reputation come from independent leaderboards; K3's headline figures don't yet. The gap usually closes within weeks — in one direction or the other.
- Benchmarks don't transfer. A two-point SWE-Bench edge tells you roughly nothing about your Django monolith. The protocol that does: five real tasks from your own git history, blind-scored.
- "Open" has fine print. These are open-weight releases, not open-source ones — weights yes, training stack no. For self-hosting that distinction rarely matters; for auditability it might.
- Data residency is your call. API = your context visits the provider, wherever it is. If that's a dealbreaker, the open-weight route on your own infra is the answer — and secrets should stay out of agent context regardless of whose model reads it.
How to actually try them (ten minutes)
You don't need five accounts. One OpenRouter key fronts the whole field. Point a provider-agnostic CLI at it — OpenCode is the natural host — pick a model string, and run your standard five-task gauntlet. Swap the string, run it again. An afternoon and a few dollars buys you a first-hand ranking that no leaderboard can.
And if what you really want is judgment rather than a new daily driver: seat two or three of them on the same hard question next to your Claude or GPT and judge the spread. Models trained by different labs failing in different ways is precisely what makes their agreement informative — that's the whole logic of cross-model checking.
Frequently asked questions
What is the best Chinese AI model for coding right now?
Per axis: GLM-5.2 for peak scores, Kimi K2.6 for long agent runs, DeepSeek V4 for price, Qwen for open adoption — and Kimi K3 as the new flagship bet while independent evals land. No single winner; a winner per workload.
Are Chinese AI models really open source?
Mostly open-weight: permissive-licensed weights (Qwen and DeepSeek most consistently), private training stacks. Kimi K3 shipped API-first with weights promised by July 27, 2026.
Is it safe to point a Chinese model at my private code?
Same calculus as any API — your context visits the provider unless you self-host. Prefer open weights on your infra if that matters, and keep secrets out of agent context no matter whose model reads it.
How close are they to GPT and Claude on coding?
Within a few points on public suites — K2.6 reports ~80 on SWE-Bench-class benchmarks, near leading US scores. But benchmarks transfer poorly; run the comparison on your own codebase.
Where Backgrind fits
A month like this is the argument for owning the layer above the models. Backgrind is an overlay over whatever CLIs you run — Claude Code on Anthropic, OpenCode on K3 or GLM or DeepSeek — in tabs, with ambient notifications, so trying a new model is a config change rather than a workflow migration. The Fusion council takes it one step further: your models, one hard question, read-only repo access, one judged verdict. When the field reshuffles every month, the winning move is to not marry anyone.
Sources
Field overview and leaderboard positions: Turing Post's 2026 guide to Chinese models, BenchLM's July 2026 ranking, and TokenMix's Q2 comparison. K3 specifics: The AI Rankings. Benchmark figures are as reported by those sources in mid-July 2026; where numbers were lab-reported we've said so.