Every few months an open-weights release forces the same board-level question: are we still paying frontier-API prices for work an MIT-licensed model can do? GLM-5.2 is the strongest version of that question yet asked, because for the first time the gap on long-horizon coding benchmarks is inside the noise floor: Z.ai's published FrontierSWE number sits 0.7 points behind Claude Opus 4.8 at output-token prices roughly a sixth of Anthropic's. This brief is the evaluation we would run before believing that, written down.
What it actually is
GLM-5.2 went to Z.ai's Coding Plan subscribers on June 13, 2026, and the full weights landed on Hugging Face under an MIT license on June 16 (announcement, model card). It is a Mixture-of-Experts transformer with 753B total parameters and roughly 40B active per token (Artificial Analysis tallies the total at 744B; both counts agree on the 40B active figure, which is what your serving economics care about). The BF16 weights are about 1.51TB on disk per Simon Willison, who called it "probably the most powerful text-only open weights LLM" the day after release.
Three architectural details matter for buyers:
- A 1M-token context window, up from GLM-5.1's 200K. The announcement credits a sparse-attention scheme called IndexShare, where every four attention layers share a lightweight indexer, for cutting per-token FLOPs by a claimed 2.9x at the 1M length.
- Text only. There is no vision input. More on why that bites in practice below.
- A multi-token-prediction layer for speculative decoding, with Z.ai claiming up to 20% better acceptance length, which is throughput you get for free on supported inference stacks.
The license, and the question behind it
MIT, full stop. No user thresholds, no attribution badges, no derivative naming rules, and the announcement goes out of its way to say "no regional limits." Against the Llama 4 Community License and its conditions, this is the shortest legal conversation in the open-weights market, the same posture as DeepSeek's MIT line.
The question clients actually ask is the China question, and the answer has two halves. The weights are inspectable files. Self-hosted in your VPC, there is no vendor in the request path and no telemetry; provenance is a supply-chain review, not a data-flow review. The first-party API is a different matter: Z.ai is a Chinese vendor, and if your data-governance posture excludes that, the practical middle path is US-based inference providers. OpenRouter routes GLM-5.2 across multiple hosts (Willison counted nine providers within a day of release, and Interconnects names Fireworks and Together among them), so you can buy the model without buying the vendor's data path. Decide which half of this you are procuring before the pilot, not after.
The benchmark story, read carefully
Z.ai's own published table is unusually specific, so quote it with attribution and the caveat that vendors choose their tables:
| Benchmark | GLM-5.2 | Claude Opus 4.8 | GPT-5.5 | |---|---|---|---| | Terminal-Bench 2.1 | 81.0 | 85.0 | 84.0 | | SWE-bench Pro | 62.1 | 69.2 | 58.6 | | FrontierSWE | 74.4% | 75.1% | 72.6% | | MCP-Atlas | 76.8 | 77.8 | 75.3 |
Read the second row as carefully as the third. On FrontierSWE (multi-hour, open-ended engineering tasks) GLM-5.2 is effectively tied with Opus 4.8 and ahead of GPT-5.5. On SWE-bench Pro, Opus 4.8 is still seven points clear. Both are true at once: this model closed most of the gap, not all of it, and which gap matters depends on your workload.
The third-party signal is what elevates this release above the usual launch-table skepticism. Artificial Analysis independently scored it 51 on their Intelligence Index v4.1, the highest of any open-weights model, ahead of MiniMax-M3 (44), DeepSeek V4 Pro (44), and Kimi K2.6 (43). Cline called it "the first open-weights model to cross 80% on Terminal-Bench." And Nathan Lambert's Interconnects write-up makes the point benchmarks cannot: "GLM-5.2 is the open weight model that feels right in coding harnesses as a general agent. It's the first one." That practitioner sentence, not the table, is why this brief exists.
Our standing advice is unchanged: these numbers earn the model a seat in your evaluation, and nothing more. Run your own task-level evals before moving traffic.
Real cost, including the verbosity tax
Verified against Z.ai's pricing page as of July 2026: $1.40 per million input tokens, $0.26 cached input, $4.40 per million output tokens. Via OpenRouter, a 35% promotional discount had it near $0.91/$2.86 at the time of writing. Against Anthropic's published Opus 4.8 rates of $5.00 input and $25.00 output, GLM-5.2's output tokens cost roughly a sixth and input just over a quarter.
Now the correction most cost models miss: GLM-5.2 spends more tokens to do the same work. Artificial Analysis measured about 43K output tokens per Intelligence Index task, 37K of it reasoning, versus 24K for MiniMax-M3 and 35K for Kimi K2.6, and roughly $0.46 per task versus $0.18 for MiniMax-M3. The per-token sticker overstates the savings and understates the latency: those thinking tokens arrive before your user sees anything. Price the model per completed task on your own workload, never per million tokens.
One more commercial tell from the announcement: Z.ai's Coding Plan meters subscription quota by time of day, with peak hours (14:00 to 18:00 UTC+8) drawing 3x quota and off-peak 2x, promotionally 1x through the end of September. Rationing is a capacity signal; demand for this model is real.
Self-hosting is a datacenter conversation. The BF16 weights are 1.51TB before KV cache, and a 1M-token context makes KV cache its own capacity line. Unsloth's community quantizations put 4-bit builds between 365GB and 467GB on disk depending on variant, and the 2-bit dynamic builds at 238GB to 254GB, the smallest of which fits a 256GB unified-memory Mac at single-digit tokens per second: a proof of ownership, not a production deployment. Production self-hosting means a multi-GPU node in the 8x 96GB-to-141GB class or larger, served through the stacks the model card lists (vLLM, SGLang, transformers, KTransformers, plus Ascend NPU support). Most teams should start on rented endpoints and let measured volume justify the hardware; MIT means that door never closes.
What breaks in production
- Text-only is an integration hazard, not just a missing feature. Modern coding harnesses casually attach screenshots; Lambert reported that his harness sending images "would brick Fireworks API for the session." Audit every image path in your agent stack before cutover.
- Verbosity is a budget and latency problem. 43K output tokens per task compounds across a multi-step agent. Cap thinking budgets per step and measure.
- Hosted-provider variance. Different hosts serve different precisions and context configurations. Pin one provider, record the precision you evaluated, and re-evaluate on any provider change.
- Ecosystem velocity cuts both ways. Interconnects flags the regulatory tail risk on Chinese open weights explicitly. Weights you hold cannot be revoked, but a hosted-only dependency on this model deserves the same fallback lane we build for every proprietary API.
When to use it, and when not
Use GLM-5.2 when:
- Your dominant spend is agentic coding or long-horizon terminal work, the exact lanes where its published and third-party results are strongest.
- You want frontier-adjacent capability with an exit ramp to self-hosting that a hosted-only frontier model can never offer.
- Cost per task, measured honestly against your incumbent, shows the verbosity-adjusted savings are real for your workload.
Do not use it when:
- Your agents need vision. There is no GLM-5.2 image input, and no bolt-on fixes that cleanly.
- Your hardest tickets live where the SWE-bench Pro gap lives; keep a frontier escalation lane rather than forcing one model to do everything.
- Tight interactive latency budgets cannot absorb 30K-plus reasoning tokens per step.
How we would architect it for a client
The engagement shape is a shadow-lane evaluation inside the same model-agnostic gateway we use for every model engineering build:
- Shadow the incumbent. Route a copy of real coding-agent traffic to GLM-5.2 on a pinned US-hosted endpoint, score both lanes on task completion, review burden, and cost per completed task over two to four weeks.
- Exploit the cache line. At $0.26 per million cached input tokens, stable prompt prefixes do the same quiet work here as on every frontier API.
- Route by difficulty, not by loyalty. The realistic end state is GLM-5.2 owning volume coding-agent traffic with a proprietary frontier model held for the tail, the same routing discipline we apply across vendors.
- Keep the self-host option priced. Because the license is MIT, a move into the client's VPC is a procurement decision, not a re-architecture. We keep the GPU sizing sheet current so the trigger is a spreadsheet threshold, not a research project.
GLM-5.2 is the first open-weights model where "replace the frontier API for coding" is a serious engineering question rather than a cost fantasy. Serious questions deserve evals, not vibes. Run them.