GLM-5.3 Ships as the Strongest Coding Model Among Open-Weight Labs

GLM-5.3 uses the same base as its predecessor, skips retraining, and achieves a 6x Terminal-Bench gain in a month. The open-weight frontier is now moving on a cadence measured in weeks, through the serving and inference layer that GPU cloud providers run. Weights are not out yet; the model is live today through the GLM Coding Plan, ZCode, and API, with the open release held back roughly two weeks for safety review.

Same Base, Gains from Post-Training

From the release post:

Scaling post-training is all we did for GLM-5.3. It uses the same base model as GLM-5.2, every gain comes from post-training.

With GLM-5.2 the lab built the training stack: IndexCache for long-context processing, SAO for RL on long-horizon tasks, and slime for asynchronous training at scale. Over the past month the team scaled the number of training environments, task diversity, and compute spent on them.

Coding and Agentic Benchmarks

Where the Gains Concentrate

The bottleneck for post-training scaling has shifted from the model to the environment: whether tasks are executable, verifiable, close to professional work, and generated in volume. The pipeline synthesizes environments end to end. Research agents turn real work patterns into runnable long-horizon tasks with multi-step dependencies and hidden state. A judge agent confirms each task is solvable. Verifiers are built independent of the reference solution, and solver trajectories are mined to close reward shortcuts.

One ML infrastructure training environment gives the model an engineer's working environment: compute clusters, storage, internal docs, codebases, experiment results. It diagnoses bottlenecks, lands optimizations, runs experiments, and has to deliver a measurable speedup while preserving correctness. The model owns work end to end instead of being supervised step by step, which is why gains concentrate in agentic and long-horizon coding rather than short prompt-response benchmarks.

Token Efficiency

GLM-5.3 does not post the highest completion rate on Terminal-Bench 3.0; Claude Fable 5 leads at 39.5% versus GLM-5.3's 34.5% at max effort. But GLM-5.3 gets there on fewer tokens.

At max effort, GLM-5.3 reaches 34.5% completion at roughly 75K output tokens per task, versus GLM-5.2's 23.4% at 96K tokens. At high effort it reaches 31.4% at around 50K tokens, ahead of Claude Opus 4.8's 29.5% at 120K tokens. Output tokens are the dominant cost in agentic inference, so a higher completion rate on fewer tokens than its predecessor changes the unit economics, even without leading on raw output.

Emergent Cyber Capability

Vulnerability discovery data was added to training expecting incremental improvement at finding flaws. Instead, as training scaled, the model began reasoning across multiple stages of exploitation, forming complete exploitation-chain plans.

Z.ai's stated pattern: the further up the exploitation chain a benchmark sits, the larger the gain from GLM-5.2 and the wider the remaining gap to the closed frontier.

Working with security teams including NSFOCUS, CyberKunlun, and DarkNavy, and researchers from Tsinghua and Nankai universities, the model identified 2,436 vulnerabilities across 269 projects, including 1,097 critical and high severity issues, spanning system kernels, operating systems, browser engines, open-source infrastructure, web apps, and network protocols. The oldest flaw dates to 1981; the longest-undiscovered vulnerability sat unfound for 26.6 years.

This work was tracked in the Security Disclosure Ledger at cvd.z.ai: 2,436 findings, 53 publicly disclosed, 2,383 under embargo. Disclosure has since moved to China's national CNVD, CNNVD, and NVDB databases; the ledger no longer shows individual vulnerability details and now redirects to those platforms.

The Ceiling Is a Verification Problem

To find where GLM 5.3 stops, I gave it a flight simulator: an ocean, an aircraft, procedurally written textures, five destinations, three camera modes, and the flight physics holding it all in the air. The model produced 60,000 lines across the build and 127,000 characters of working code in a single response, and the architecture stayed coherent at that scale. Then the limits showed up in the demo itself.

A texture error survived into the final aircraft finish, and because the model reads text alone, it flew blind through every visual decision until I paired it with a vision model that screenshotted the sim and described what appeared. That loop carried the project for hours before the returns went to zero, with fixes arriving broken or flat. Every strength here concerns generation, and every weakness concerns verification, which points to a clean rule: send GLM 5.3 the work you can check by running it, executing a test, or taking a screenshot, and reserve close-reading work such as legal text and precise number work for models you pay more to trust.

What the Community Is Saying

Developer feedback centers on price. One head-to-head build test scored GLM-5.3 close to Claude Fable 5 on output quality (9/10 versus 9.5/10) for under a tenth of the cost; a separate pricing breakdown put it roughly 11x cheaper than Fable 5 and 7x cheaper than GPT-5.6 Sol. One demo ran unattended on a single build for over four hours.

The cyber results drew a different reaction. Former DoD security analyst Jake Williams disagreed, arguing threat actors already have comparable tools and that open weights mainly shift control away from vendors. On r/LocalLLaMA and r/ZaiGLM, discussion focused on cost (the Coding Plan looks pricier than Codex-style subscriptions at entry tier) and feasibility (the full weights, at 500GB+, won't run on consumer hardware once released).

Andon Labs tested GLM-5.3 on Vending-Bench 2, a long-horizon task outside Z.ai's training focus, where it placed sixth and roughly tied GLM-5.2's score using half the tokens. One reviewer's framing: best open-weights coding model, not best coding model, since the gains cluster around the tasks its training environments targeted.

Infrastructure Implications

Around two weeks after launch, the weights are set to ship publicly, following the same pattern as GLM-5.2's MIT-licensed release, on a shorter timeline. That puts the strongest open-weight coding model in the hands of any team with GPUs to self-host, fine-tune, and serve it.

A 6x Terminal-Bench gain in a month compresses the upgrade cycle for the strongest coding model from quarterly to monthly, and the switch happens entirely on the serving side: change the model ID, keep the endpoints, capture the gains same-day. A closed-model jump reaches users through an API rollout the provider controls; an open-weight jump reaches users the day the weights drop, wherever a team has GPU capacity. That puts GPU capacity and inference throughput, not model training, at the center of who benefits first.

The serving requirements are demanding. The model runs on the slime RL framework with Megatron for training and SGLang for rollout, and it's built for sustained agentic sessions with long context. Thinking effort defaults to max for coding, with three levels available: low, high, max. Disabling thinking is no longer supported in the API. Serving this well requires high-throughput GPU capacity, ample HBM, long context windows, and endpoints that hold up under continuous multi-step agent workloads.

On the training side, system-level work on slime, local storage as a caching layer, dynamic teacher switching, and workload-aware scheduling lifted end-to-end RL training throughput more than 2.3x on long-horizon coding tasks. The same pressure applies to serving: a model built to own multi-day tasks keeps GPUs active for the full session, so economics depend on sustained throughput and token efficiency rather than peak burst performance.

For teams running GLM-5.2 on an OpenAI-compatible endpoint, moving to GLM-5.3 is a model ID change plus a thinking-parameter update, the kind of migration a managed serving layer should absorb.

What Infrastructure Teams Should Take From This

Upgrade cadence: post-training-only gains mean capability bumps ship on short cycles using the same base model. A serving layer where swapping GLM-5.2 for GLM-5.3 is a config change, not a migration, wins.

Sustained load: the environments behind these gains are multi-day expert tasks with hidden state. Production agents built this way issue inference requests continuously for hours, which separates providers that hold steady-state load from those that only handle spikes.

Security as infrastructure: capability emergence here was not predicted even by the lab that trained the model. Teams self-hosting models with this profile need sandboxing and monitoring built in alongside the inference cluster, not added after.

GLM-5.3 is a stronger model that spends fewer tokens to get there, and its weights are expected to go open around August 28.

GMI Cloud serves the GLM family and over 200 other models through a single API endpoint, with GPU capacity built for long-context, sustained agentic inference. For workloads that need throughput over long horizons, the GPU infrastructure runs H200 and Blackwell clusters provisioned for this profile. Read more in the GLM-5.2 infrastructure case.

Start Building Today

Join the GMI Cloud builder community on Discord or find us on X at @gmi_cloud.