Introducing GLM-Legal Built on GLM-5.3-Flash, GLM-Legal matches frontier models on mainstream legal benchmarks. Designed for real legal workflows: contract review, evidence analysis, compliance, and more. Tech Blog: z.ai/blog/glm-legal Apply for API Access: z.ai/consultation/legal Try AutoClaw: autoclaw.z.ai

New journey, new mission! Thrilled and grateful for the opportunity to help build a safer cyberspace with the power of frontier AI @Zai_org

See GLM-Legal in action

Zai just debuted a legal specific model: GLM Legal, and it is the new #1 open-weight model on Harvey’s Legal Agent Benchmark and LegalBench.

GLM-5.3 is now available on Amazon Bedrock. Bring powerful coding and agentic capabilities to your enterprise. Get started: docs.aws.amazon.com/bedrock/…

GLM-5.3 has helped defend 389 open-source projects, with 4,249 potential vulnerabilities found so far. OpenVuln is still running. The service remains free, and findings go privately to maintainers. huggingface.co/spaces/zai-or…

All GLM Coding Plan users have received 4 weekly reset cards and 4 five-hour reset cards (usable in all supported agents). Users returning within the next month will receive the same benefits.

Faster GLM-5.3-Flash is now live: up to 200 tokens/s. Model code: glm-5.3-flashx. Priced at 2.5× GLM-5.3-Flash on both the Coding Plan and API. Open to all API users. Coding Plan users can apply here: docs.google.com/forms/d/e/1F…

ZCode is now open source under the Apache 2.0 license. github.com/zai-org/ZCode

In response to the ZCode product security issues reported by the community, we have completed the necessary remediation and sincerely apologize to all our users. We have open-sourced ZCode at github.com/zai-org/ZCode, placing the code under community scrutiny and making ZCode more open and transparent. We sincerely thank the community developers who previously identified issues in ZCode. Going forward, we will establish an ongoing product security vulnerability reporting and response process. We welcome developers to continue reviewing ZCode and reporting potential issues, and we will provide rewards based on the severity of the issues reported. With respect to the code data referenced by the community, we confirm that no such data is retained and that it has never been used for model training. Following the remediation, we invited the China Academy of Information and Communications Technology (CAICT) and NSFOCUS to conduct security assessments. The results are as follows: Through its technical assessment, CAICT confirmed that the zcode-prod Alibaba Cloud OSS bucket is in a zero-data state. Security remediation has been completed in the ZCode v3.14.0 client. The Repo Wiki feature has been removed, and the workflow for generating and uploading local repository snapshots has been disabled. NSFOCUS confirmed that all data objects in the zcode-prod Alibaba Cloud OSS bucket, as well as the bucket itself, have been deleted. Remediation has been completed in the ZCode v3.14.0 client. The Repo Wiki entry point and the associated generation workflow have been removed, and no functional path capable of triggering the generation of local repository snapshots or transmitting local files externally was identified. Once again, we sincerely apologize and welcome continued scrutiny from the community. The full security assessment report will be released soon.

Two weeks. That's how long it took to go from GLM-5.3-Flash's first run on domestic accelerators to serving all of its production traffic, with 3.2× end-to-end throughput along the way. What I keep thinking about is who did much of the work: an Infra Agent powered by GLM-5.3. A model helping optimize the system that serves it. The conditions were hard. Limited memory and interconnect bandwidth. 1M-token context. Multimodal requests. An immature software stack where kernels were missing and documentation was often guesswork. Every optimization was a trade: compute for memory (ReplaySSM), communication for memory (intra-node tensor parallelism), precision for capacity (mixed INT8/FP8/BF16 caching), and disaggregation for scheduling freedom (Encode–Prefill–Decode). But the most important lesson wasn't about any single optimization. When the agent got stuck, it was rarely because it couldn't write the code. It was because it didn't know *why* things got worse. "Throughput down 20%" tells you something broke. It doesn't tell you which layer, which hypothesis, or what to test next. In RL terms, it's a sparse reward with a credit assignment problem. And an end-to-end benchmark that takes hours makes exploration painfully slow. Senior engineers solve this with an implicit process reward in their heads. They know when to check the timeline, when to run a microbenchmark, and which layer's output to compare. So we made that explicit. We call it dense feedback: layered verification interfaces the agent can call directly. Correctness feedback: did it compute right? System behavior feedback: where did the time go? Performance feedback: which option wins, under which conditions? Each signal has to be local, cheap, and objectively verifiable. Three things the agent found: First, precision drift in KDA's context-parallel path that grew with sequence length. The cause was TF32 rounding error compounding through chained state-matrix merges. The fix is now merged upstream in Flash Linear Attention (PR #1180). Second, KV transfer never overlapped with DeepEP dispatch. The agent followed the call chain across the Python/C++ boundary and found that the intranode path never released the GIL. After the fix, transfer overhead fell from over 30% to under 1%. Third, a decode kernel recomputing the same normalization four times because of how it was chunked. The agent restructured it and got a 1.71× speedup. The idea came from "optimization skeletons" it had distilled by reading existing kernels across SGLang, FLA, and DeepGEMM. To be clear about the boundaries: humans still defined the goals, built the feedback environment, and reviewed every high-risk change. But the engineer's role is changing, from the person who solves the problem to the person who designs the feedback. There's a deeper implication too. A layered, verifiable feedback environment built on real infrastructure tasks is exactly what training the next generation of models needs most. Every task the agent completes can become training ground for its successor. We are still far from recursive self-improvement. But the smallest loop now exists. The model optimizes the system. The system serves the model.

We’re sharing how GLM-5.3 helped build and optimize the inference infrastructure serving GLM-5.3-Flash. The system went from its first successful run to production readiness in less than two weeks, with end-to-end throughput tripling relative to the initial baseline. The key was dense feedback: local correctness tests, execution traces, microbenchmarks, and end-to-end measurements that enabled targeted hypothesis testing rather than reliance on aggregate performance metrics alone. z.ai/blog/glm-built-its-infe…

AI is global. The next phase of AI adoption will be shaped by local infrastructure, local expertise, and strong ecosystem partnerships. Today, we're introducing the Z.ai Sovereign Partner Program (ZSP) , a strategic program for partners looking to bring GLM to their countries and build local AI capabilities with Z.ai. ZSP partners will work directly with our teams across: → Early access to upcoming GLM model releases → FDE support and joint engineering → Joint go-to-market and enterprise engagement → Local token business development → Joint launches and market activation Our goal is simple: enable partners to deploy GLM on infrastructure they operate, serve customers locally, and build long-term AI capabilities in their countries. We're now selecting the first cohort of ZSP launch partners. Apply → lnkd.in/gsCRn_Um #ZSP #GLM #SovereignAI #EnterpriseAI #AIInfrastructure

Highly recommend this pricing chart and site by @Fei2411. It compares subscription and coding-plan unit prices, then rebuilds public-leaderboard Pareto frontiers from each model's lowest available price. GLM-5.3-Flash with 2x quota from 8am to 6pm PT averages about $0.0045 now. Outside that window, off-peak is about $0.0089. Site: real-api-pricing.vercel.app GitHub: github.com/FeiZhuLulu/real-a…

Can't believe four GLM-5.3-Flash events are running now: 1. ZCode + GLM Coding Plan Unlimited, 8AM–6PM PT daily 2. Other agents + Coding Plan 2x quota during the same window 3. ZCode 300M free tokens this weekend (FCFS) 4. AutoClaw 100M free tokens for new users

GLM-5.3-Flash has been live for a week. If we only improve one thing next, what would make it your default?

We’re still up.

Get more GLM-5.3-Flash with GLM Coding Plan ⏲️ 8 AM–6 PM PT every day, Sep 3–20 - In ZCode: Unlimited GLM-5.3-Flash - In other supported agents: 2× Flash quota

GLM Coding Plan turns one year old today. To celebrate, we're giving every current subscriber a Reset Card. Use it to refill both your weekly and 5-hour quotas. Thanks for using GLM, helping shape it, and pushing it to its limits. - Personal plan: z.ai/manage-apikey/coding-pl… - Team plan: z.ai/manage-apikey/coding-pl…

ZCode users will continue to enjoy a 150% usage allowance on GLM Coding Plan.