GLM-5.3 Kept the Same Base Model—Where Did Its Coding Gains Come From? An In-Depth Look at Post-Training (The New Stack)

Core content summary

Z.ai released GLM-5.3 on August 14. It shares the same base model as GLM-5.2, with all gains coming from post-training. Developers can already use GLM-5.3 in Claude Code, Cline, OpenCode, and Codex through the GLM Coding Plan; direct API access is marked as “coming soon,” and the weights will be released after two weeks of hardening and safety testing.

What post-training did

• Z.ai substantially expanded post-training, exposing the model to ten times as many long-horizon task environments as before and broadening its access to developer tools and engineering workflows.

• Some training tasks simulate the full software lifecycle—from identifying a bug and drafting a fix to writing code, running tests, and delivering the result. A single task is equivalent to several days of work by a senior engineer.

• The core idea: concentrate compute on the environments where the model actually works. The author draws a parallel with DeepSeek: rather than inflating the parameter count, optimize post-training so that a smaller model can outperform a flagship model.

• The author positions GLM-5.3 as “a compelling case study for post-training compute scaling” (an excellent case study for scaling post-training compute).

Benchmark gains and caveats

• Vendor-reported: internal Code Bench improved 50% over 5.2 (this self-reported figure still needs to be validated by the community once the weights are available).

• Public benchmarks: Terminal-Bench 3.0, 4.6 → 28.3; DeepSWE v1.1, 46.2 → 66.9 (tied with Google Gemini 3.7 Flash at 65%, but the test harnesses differ, so cross-model comparisons require caution); Agents' Last Exam, 23.8 → 28.5.

Practical engineering takeaways (valuable in practice for developers)

• 1M-token context + a 128K output limit; in Claude Code, the glm-5.3[1m] model tag plus a 1M-token compaction-window configuration can enable a large context window.

• There are three reasoning-effort tiers—low/high/max (max is the default). The author recommends max for nontrivial engineering tasks, but warns that latency and token costs are significant. Teams need to assess whether the downstream accuracy is worth the compute cost; official per-token pricing has not yet been announced.

• Migration note: According to the official documentation, requests in the Coding Plan that call GLM-5.2 or GLM-5.1 are automatically redirected to GLM-5.3. This is a blind spot for teams seeking a clean A/B comparison, so be sure to verify the model ID actually returned by the agent.

• Credit-based metering: GLM-5.3 has higher input/cached-input/output multipliers than GLM-4.7, but there is a 50% discount during off-peak periods, including weekends.

Analysis of safety capabilities

• CyberGym: 84.5% (5.2: 77.2%), slightly above Mythos 5 (83.8%) and GPT-5.6 Sol (83.6%).

• ExploitBench doubled from 24.4% to 54.4%, but still trails Mythos 5 (78%) and GPT-5.6 Sol (76.5%).

• The author warns that high white-box review scores deserve a question mark: reliably crafting an exploit, proving real-world reachability in production, and patching the flaw without triggering regressions are entirely different challenges. The pattern is consistent with that of frontier labs (OpenAI once delayed the release of a security model because of concerns about offensive capabilities).

• Only after the weights are released in two weeks will it be possible to verify whether the benchmark scores transfer to local deployment and different inference stacks. The gap between “open weights announced” and “weights you can actually run” has become a recurring pattern in the open-source model community (Kimi K3 followed a similar cadence).

Key quotes from the original

"This makes GLM-5.3 a compelling case study for post-training compute scaling. Z.ai concentrated compute on the specific… This is a necessary excerpt; read the original source for full context.

"Reliably crafting an exploit, proving real-world reachability in production, or patching the flaw without triggering do… This is a necessary excerpt; read the original source for full context.