GLM-5.2 Just Broke the 80% Barrier on Terminal-Bench

Published June 21, 2026.

Z.ai released GLM-5.2 on June 13, 2026, a 744-billion-parameter Mixture-of-Experts model that scored 81.0% on Terminal-Bench 2.1. No open-weights model had crossed 80% on this benchmark before. The result puts GLM-5.2 within striking distance of proprietary frontier models on the most demanding test of autonomous coding ability available today, and it ships under an MIT license.

The jump matters because Terminal-Bench 2.1 is not a code-completion quiz. It drops an agent into a containerized environment, hands it a multi-step task (fix a broken build, resolve a Git conflict, configure a server), and checks the final state programmatically. No partial credit. The benchmark is the closest public proxy for whether a model can actually do the work, not just talk about it.

GLM-5.2's predecessor, GLM-5.1, scored 62% on the same benchmark. An 81% result in a single generation is a 19-point swing.

What Happened

Z.ai, the international brand of Zhipu AI, shipped GLM-5.2 as an open-weights release on June 13. The model is available on the Z.ai API, Hugging Face, and through Ollama for local inference.

The core numbers:

• Terminal-Bench 2.1: 81.0% (up from 62% for GLM-5.1)
• Parameters: 744B total (MoE), approximately 40B active per token
• Context window: 1,000,000 tokens, native
• License: MIT, unrestricted commercial use
• FrontierSWE: Trails Claude Opus 4.7 vs GPT-5.5: Four Questions That Decide It subjects by roughly 1% while edging GPT-5.5 by 1%
• PostTrainBench: Second only to Opus 4.8

The architectural headline is IndexShare, a new optimization that reuses the same sparse-attention top-k indexer across every four transformer layers. Z.ai claims this cuts per-token FLOPs by 2.9x at 1M context length compared to standard sparse attention approaches like DeepSeek's DSA.

GLM-5.2 also ships an improved Multi-Token Prediction (MTP) layer that increases speculative decoding acceptance length by up to 20%, which translates to faster inference on compatible serving stacks.

Why 80% on Terminal-Bench Is the Number That Matters

Terminal-Bench 2.1 tests whether a model can function as an autonomous coding agent across software engineering, system administration, data science, and security tasks. It is binary pass/fail with programmatic verification. Crossing 80% means GLM-5.2 can reliably solve four out of five real-world terminal tasks without human intervention.

For context, the gap between proprietary and open-weights models on this benchmark has historically been 15 to 25 points. Claude Opus 4.8 and GPT-5.5 sit in the low-to-mid 80s. GLM-5.2 landing at 81% collapses that gap to noise.

This is a different story from DeepSeek V4 vs Opus 4.7 vs GPT-5.5: Cost Beats Lag, where DeepSeek V4 competed on cost but still trailed on raw agentic capability. GLM-5.2 competes on both capability and openness.

Does IndexShare Actually Change the Cost Equation?

A 2.9x reduction in per-token FLOPs at long context is significant, but comes with a caveat. The efficiency gain scales with context length. At short context (under 8K tokens), the improvement is marginal. At 256K and above, the savings compound because reusing the sparse-attention indexer avoids redundant computation across layers.

For teams running Codex vs Claude Code vs Gemini CLI that routinely pass 100K+ tokens of repository context into the model, IndexShare could meaningfully reduce inference costs. For chat-style interactions at 2K tokens, the architecture is less of a differentiator.

Z.ai has not published detailed latency benchmarks or pricing comparisons against Opus 4.8 or GPT-5.5 at equivalent workloads. The 2.9x number comes from the technical report and has not been independently verified at scale.

What the Community Is Actually Saying

The r/LocalLLaMA community has been testing GLM-5.2 since release, and the reaction is a mix of genuine excitement and practical concern.

The excitement is straightforward: a model that competes with Claude Opus 4.8 on coding benchmarks, ships under MIT, and can be self-hosted is exactly what the open-weights community has been waiting for. Multiple developers have reported strong results on real-world projects, calling it a "game changer" for locally-hosted agentic coding.

The concern is what the community calls "thinkslop." GLM-5.2 tends to produce verbose internal reasoning chains before generating its answer. On complex tasks, this depth of thinking improves accuracy. On simpler tasks, it burns tokens and adds latency without improving output quality. The tradeoff is familiar to anyone who has used extended thinking models, but GLM-5.2's tendency is reportedly more aggressive than Opus or GPT-5.5.

Hardware is the other friction point. A 744B-parameter model, even as an MoE with 40B active, requires serious GPU infrastructure for local inference. Quantized versions via Unsloth are available for smaller setups, but the full-precision model needs multiple high-end GPUs.

Who This Affects

Self-hosting teams and solo developers: This is the primary audience. GLM-5.2 under MIT means you can run a frontier-competitive coding agent on your own infrastructure with no API dependency, no usage caps, and no vendor lock-in. If you have the hardware (or can rent it), the cost equation shifts dramatically compared to paying per-token for Opus 4.8 or GPT-5.5.

Agentic coding tool builders: Teams building products like Antigravity or Claude Code now have a credible open-weights backbone to offer customers who want data sovereignty or air-gapped deployments. The Terminal-Bench result gives GLM-5.2 the credibility that earlier open models lacked.

Anthropic and OpenAI: The competitive pressure from open-weights just got sharper. When the best open model was 15 points behind on Terminal-Bench, the value proposition for proprietary APIs was clear. At a 1-point gap, the pitch shifts from "our model is better" to "our ecosystem is better." That is a harder argument to make to cost-sensitive teams.

What to Watch For Next

The 81% number is from Z.ai's own evaluation. Independent verification on Terminal-Bench 2.1 typically takes 2 to 4 weeks as third-party labs run the benchmark with different agent harnesses. If the score holds or improves with optimized agent scaffolding, the open-weights narrative shifts permanently.

Watch for Anthropic's and OpenAI's response. When Ideogram opened its weights for 4.0, it accelerated the image generation market. A similar dynamic in coding agents would force pricing pressure on proprietary APIs within 90 days.

The thinkslop issue is likely a post-training tuning problem, not an architectural one. Z.ai will probably ship a version with tighter reasoning budgets within 30 days. If they do, the token-efficiency concern mostly disappears.

The Bottom Line

GLM-5.2 is the first open-weights model to match proprietary frontier models on the hardest autonomous coding benchmark. The 81% Terminal-Bench score, combined with MIT licensing and a 1M-token context window, makes it the most compelling open-weights coding model released in 2026. The caveats are real (hardware demands, thinkslop, unverified efficiency claims), but the signal is clear: the gap between open and closed on agentic coding just closed.

FAQ

How does GLM-5.2 compare to DeepSeek V4 on coding benchmarks?

GLM-5.2 scores 81% on Terminal-Bench 2.1, which is currently the highest among open-weights models. DeepSeek V4, while competitive on cost and general reasoning, has not matched this score on Terminal-Bench specifically. GLM-5.2 also leads on PostTrainBench and trails DeepSeek V4 on some general reasoning tasks.

Can I run GLM-5.2 locally?

Yes, but you need substantial hardware. The full 744B-parameter model requires multiple high-end GPUs. Quantized versions are available through Unsloth and Ollama for smaller setups, though with some quality tradeoff. The 40B active parameters per token (thanks to MoE) mean inference is less demanding than a dense 744B model would be.

What is Terminal-Bench 2.1 and why does 80% matter?

Terminal-Bench 2.1 is an industry-standard benchmark that tests AI agents on real-world CLI tasks: compiling code, debugging builds, configuring servers, and reverse engineering. It uses programmatic verification with no partial credit. Crossing 80% means the model solves four out of five complex terminal tasks autonomously, a threshold previously held only by proprietary models.

Is GLM-5.2 truly open-source?

GLM-5.2 is open-weights under MIT license, which allows unrestricted commercial use, self-hosting, and modification. The training data and full training pipeline are not released, so it is open-weights rather than fully open-source by the strict definition. For most practical purposes, the MIT license provides maximum freedom.