Long-horizon coding benchmarks
FrontierSWE, PostTrainBench, SWE-Marathon — GLM-5.2 vs the frontier.
About this data
GLM-5.2 trails Claude Opus 4.8 by about 1% on FrontierSWE while edging out GPT-5.5, and ranks second only to the Opus series on PostTrainBench and SWE-Marathon. Across all three long-horizon benchmarks it is the highest-ranked open-source model — the core claim of the launch, that a usable 1M context translates into real multi-hour delivery.
Score (higher = better). GLM-5.2 trails Opus 4.8 narrowly and is the top open-source model.
View data & sources →Data table
| glm51 | glm52 | gpt55 | gemini | opus48 | series | benchmark | source_ref | value_basis |
|---|---|---|---|---|---|---|---|---|
| 30.5 | 74.4 | 72.6 | 39.6 | 75.1 | coding_long | FrontierSWE | zai-glm52 | Full Benchmark Table — FrontierSWE (dominance as of 2026-06-16) |
| 20.1 | 34.3 | 28.4 | 21.6 | 37.2 | coding_long | PostTrainBench | zai-glm52 | Full Benchmark Table — PostTrainBench |
| 1 | 13 | 12 | 4 | 26 | coding_long | SWE-Marathon | zai-glm52 | Full Benchmark Table — SWE-Marathon |
Methodology & sources
Last updated: Jul 17, 2026Methodology
Source-backed values for all six charts come from the Z.ai GLM-5.2 launch post (2026-06-16): long-horizon coding (FrontierSWE, PostTrainBench, SWE-Marathon), standard coding (Terminal-Bench 2.1, SWE-bench Pro, NL2Repo, DeepSWE, ProgramBench), reasoning (HLE, CritPt, AIME, HMMT, GPQA-Diamond, IMOAnswerBench), agentic (MCP-Atlas, Tool-Decathlon), the GLM-5.2 vs GLM-5.1 generational leap, and the MTP acceptance-length ablation. Every numeric point carries a sources[].ref and a value_basis naming the table row. Scores are reproduced verbatim from the Full Benchmark Table; cells the vendor published as "-" (not reported) are omitted, never estimated. CAVEAT: these are the model developer’s self-reported figures under their stated harnesses and prompts (see the post’s footnotes); some competitor HLE/CritPt cells are full-set scores. They are comparison-as-published, not an independent eval. Architecture context (not charted): 1M-token context (up from 200K), IndexShare cuts per-token indexer FLOPs ~2.9× at 1M, MIT-licensed open weights. Re-verified 2026-06-22.
Comparisons are informative, not definitive. See each source for definitions and limits.