
What changed from GLM 5.2 to GLM 5.3
Z.ai built GLM-5.3 on the same base model as GLM-5.2. It did not retrain from scratch.
Post-training is the stage after pretraining, where a finished model is trained further on tasks and rewarded for correct results. Z.ai says it spent the month before launch scaling that stage: more training environments, more varied tasks, and more compute spent on them.
The company's headline claim is a 50% improvement over GLM-5.2 on Z.ai Code Bench. That benchmark is Z.ai's in-house test, so the 50% is the vendor's own figure. The other benchmarks named in the same post move the same way:
- Terminal Bench 3.0 rises from 4.6 to 28.3, about six times higher.
- DeepSWE v1.1 rises from 46.2 to 66.9.
- Agents' Last Exam rises from 23.8 to 28.5.
Terminal Bench 3.0 is the big jump. GLM-5.2 scored 4.6 on it and GLM-5.3 scores 28.3 on the same base. The model that came before it is covered in GLM 5.2 benchmarks, pricing, and Claude Code setup.
"It uses the same base model as GLM-5.2 — every gain comes from post-training."/"Over the past month we kept scaling on this stack: more environments, more diverse tasks, and more compute spent training on them."/"GLM-5.3 is the most capable open-weights model for coding, with a 50% improvement over GLM-5.2 on our in-house Z.ai Code Bench."/"GLM-5.3 improves from 4.6 to 28.3 on Terminal-Bench 3.0, from 46.2 to 66.9 on DeepSWE v1.1, and from 23.8 to 28.5 on Agents' Last Exam."View official source →
GLM 5.3 benchmarks against Opus 4.8 and Kimi K3
Z.ai's own table puts GLM-5.3 ahead of Opus 4.8 on five of the seven rows below. The rows cover coding, security and tool use, and every number comes from Z.ai's own runs.
Z.ai's comparison table, selected rows (vendor-run)
| Benchmark | GLM-5.3 | GLM-5.2 | Kimi K3 | Opus 4.8 |
|---|---|---|---|---|
| Terminal Bench 2.1 | 88.2 | 81.0 | 88.3 | 85.0 |
| Terminal Bench 3.0 | 28.3 | 4.6 | 17.4 | 21.1 |
| DeepSWE v1.1 | 66.9 | 46.2 | 67.5 | 58.0 |
| SWE-Marathon v1.1 | 42.5 | 19.4 | 48.1 | 48.8 |
| Toolathlon Verified | 73.0 | 59.9 | 76.5 | 76.2 |
| CyberGym | 84.5 | 77.2 | 80.0 | 78.1 |
| ExploitBench | 54.4 | 24.4 | 32.2 | 40.0 |
GLM-5.3 beats GLM-5.2 on every row. Opus 4.8 is behind it on five of the seven rows and ahead on SWE-Marathon v1.1 (48.8 against 42.5) and Toolathlon Verified (76.2 against 73.0).
Kimi K3 gives a split result. GLM-5.3 leads it on Terminal Bench 3.0, CyberGym and ExploitBench, and trails on the other four rows.
GPT-5.6 Sol scores higher than GLM-5.3 on Terminal Bench 3.0 (34.6 against 28.3) and DeepSWE v1.1 (72.7 against 66.9), among other rows. Kimi K3 benchmarks, pricing and open weights covers that model.
"| Terminal Bench 2.1 | 88.2 | 81.0 | 88.3 | 87.9 | 86.6 | 85.0 | 88.0 | 88.8 |"/"| Terminal Bench 3.0 | 28.3 | 4.6 | 17.4 | - | - | 21.1 | 33.7 | 34.6 |"/"| DeepSWE v1.1 | 66.9 | 46.2 | 67.5 | 62.7 | 56.6 | 58.0 | 69.7 | 72.7 |"/"| SWE-Marathon v1.1 | 42.5 | 19.4 | 48.1 | - | - | 48.8 | 33.1 | 42.5 |"/"| Toolathlon Verified | 73.0 | 59.9 | 76.5 | 74.1 | 72.5 | 76.2 | 74.7 | 74.9 |"/"| CyberGym | 84.5 | 77.2 | 80.0 | 83.3 | 78.5 | 78.1 | 83.8 | 83.6 |"/"| ExploitBench | 54.4 | 24.4 | 32.2 | - | 28.8 | 40.0 | 78.0 | 76.5 |"View official source →
Does GLM 5.3 use fewer tokens than Opus 4.8?
Yes, on Z.ai's own coding test. At High effort, GLM-5.3 scores 31.4% using about 50K output tokens per task. Claude Opus 4.8 scores 29.5% and uses 120K.
Effort is the setting that tells the model how long to think before answering, and the API offers low, high and max. At Max effort, GLM-5.3 reaches 34.5% at roughly 75K output tokens, while GLM-5.2 reaches 23.4% at 96K.
Z.ai Code Bench score by model and effort level
Bars show the percentage score on Z.ai's in-house benchmark (vendor-run). Labels give output tokens per task where Z.ai states them.
Output length matters because the Coding Plan counts output tokens in its points. Z.ai also states the limit of the claim: Claude Fable 5 reaches 39.5% at Max effort and stays ahead of GLM-5.3.
"At Max effort, GLM-5.3 reaches 34.5% at roughly 75K output tokens per task, compared with 23.4% at 96K for GLM-5.2."/"At High effort, GLM-5.3 reaches 31.4% at around 50K output tokens, surpassing Claude Opus 4.8 at 29.5% with 120K. GLM-5.3 remains behind Claude Fable 5, which reaches 39.5% at Max effort."View official source →
Security: leads on CyberGym, trails on ExploitBench
GLM-5.3 posts the best CyberGym score listed, but trails the closed models on ExploitBench. CyberGym gives a model a project's source code and asks it to find a flaw and prove it by triggering a fault.
GLM-5.3 scores 84.5%, up from 77.2% for GLM-5.2. Z.ai calls that the best result on the benchmark, ahead of Mythos 5 at 83.8% and GPT-5.6 Sol at 83.6%.
ExploitBench asks for deeper reasoning about real vulnerabilities and how they are exploited. GLM-5.3 reaches 54.4%, more than double GLM-5.2's 24.4%, while Mythos 5 and GPT-5.6 Sol score 78.0% and 76.5%. Z.ai's reading is that the further along the exploit chain a test sits, the larger the gain over GLM-5.2 and the wider the gap to the closed models.
Security benchmark scores from Z.ai's launch post
Bars show percentage scores (vendor-run). Mythos 5 is the name the security section uses for the model the table calls Fable 5.
One naming detail: the comparison table calls that closed model Fable 5, while the security section calls it Mythos 5. The two columns carry the same values, 83.8 on CyberGym and 78.0 on ExploitBench, and the post does not explain the difference in names.
Z.ai also says that, after expert review and deduplication, the model found 2,436 vulnerabilities across 269 projects. Of these, 1,097 are rated medium or high severity. Many had gone unnoticed for years or even decades, the oldest for roughly 40 years.
"As part of post-training, we introduced vulnerability discovery data and environments into the training mix."/"On CyberGym, which starts from white-box source code and tests whether the model can identify and validate vulnerabilities by triggering faults, GLM-5.3 scores 84.5%, up from GLM-5.2's 77.2% — the best result on the benchmark, ahead of Mythos 5 (83.8%) and GPT-5.6 Sol (83.6%)."/"On ExploitBench, which requires deeper reasoning about real vulnerabilities and their exploitation, GLM-5.3 reaches 54.4%, more than doubling GLM-5.2's 24.4%, while Mythos 5 and GPT-5.6 Sol score 78.0% and 76.5%, respectively."/"The pattern across the three is consistent: the further up the exploitation chain a benchmark sits, the larger the gain from GLM-5.2 — and also the wider the remaining gap to the closed frontier."/"After expert review, screening, and deduplication, the model identified 2,436 vulnerabilities across 269 projects, including 1,097 medium-to-high severity issues."/"Many had remained unnoticed for years or even decades, with the oldest dating back roughly 40 years."View official source →
Independent results from the Ed-o-meter
On the independent Ed-o-meter, GLM-5.3 is the first model on the board to clear all five task categories. Reinvently runs the Ed-o-meter and puts several models through the same 28 real-world tasks, split into coding, data, real work, security and tool use. Unlike the other figures, it does not come from the model's maker.
GLM-5.3 passed 100% of the tasks with a rubric score of 9.3 out of 10. The full run cost $0.28, about a fifth of gpt-5.5's $1.43. The catch is a slower start: a median of 16.3 seconds to the first token, against 13.2 seconds for gpt-5.5.
Reinvently adds its own warning. It ran a limited number of trials, so the confidence interval is wide and the scores do not separate models to the decimal. Treat the result as a signal that GLM-5.3 holds up outside Z.ai's own tests, not as a ranking.
"glm-5.3 is the first model on the board to clear all five corners — coding, data development, realworld, security and tasks — at 100%."/"As we only had a limited number of trials there is a wide Wilson interval — the whiskers on the chart."View official source →
GLM 5.3 pricing: the points-based Coding Plan
The launch post gives no per-token price for GLM-5.3. It gives a quota system instead.
The GLM Coding Plan now runs on points, counted separately for input, cached input and output tokens. Z.ai rolled GLM-5.3 out to all Coding Plan users and says it can be tried in ZCode, Claude Code, OpenCode and other coding agents.
Time of day changes the cost: calls outside peak hours use half the standard points. Peak is 14:00-18:00 UTC+8, Monday through Friday. That is four hours a day on weekdays, so every other hour, weekends included, costs half.
For ZCode, the post claims a cache hit rate of 98% or more. Repeated context is billed at the lower cached rate, which Z.ai says gives about 30% more effective tokens.
"The new GLM Coding Plan now uses a points-based quota system. Point usage is calculated separately for input, cached input, and output tokens. Model calls made outside peak hours consume 50% of the standard points. Peak hours are 14:00–18:00 (UTC+8), Monday through Friday; all other hours, including weekends, receive the 50% off-peak rate."/"98%+ cache hit rate — repeated context billed at the lower cached rate, ~30% more effective tokens"View official source →
API changes: thinking can no longer be disabled
GLM-5.3 offers three thinking effort levels, low, high and max, and no longer lets you turn thinking off. A client that still sends thinking.type set to disabled will fail once it points at the new model. Migrate in this order:
- Set
thinking.typetoenabledandreasoning_efforttolow. - Change the model ID to
glm-5.3. - For coding work, move
reasoning_efforttomax, which Z.ai recommends.
The order matters. A request that still disables thinking fails once the model ID changes. Z.ai sets low as the level for the switch and recommends max for coding.
"Disabling thinking is no longer supported by GLM-5.3."/"change it to enabled and set reasoning_effort to low before updating the model ID to glm-5.3."/"Otherwise, the request will fail."View official source →
Are the GLM 5.3 weights available?
Yes. Hugging Face lists a zai-org/GLM-5.3 repository and a BF16 build of it, both created on August 25, 2026.
Their license tag is "other", not MIT, so the license text on the model page is the document to read before commercial use. Z.ai's launch post promised the weights two weeks after launch, and August 25 falls inside that window.
Don't confuse Flash with the flagship. GLM-5.3-Flash is a separate model with its own repositories, also created on August 25, 2026, under the MIT license. When a report says "the GLM-5.3 weights are out", check whether it means the flagship or Flash.
"We will release the weights in two weeks after launch, once safety evaluation and hardening are complete."/"The model weights of GLM-5.3 will be publicly available soon in two weeks."View official source →
"id":"zai-org/GLM-5.3" … "license:other" … "createdAt":"2026-08-25T06:42:50.000Z"/"id":"zai-org/GLM-5.3-BF16" … "license:other" … "createdAt":"2026-08-25T06:43:55.000Z"/"id":"zai-org/GLM-5.3-Flash" … "license:mit" … "createdAt":"2026-08-25T06:43:14.000Z"View official source →
Use GLM 5.3 through the API or host the weights yourself
If you pay per token for agentic coding, the API is the simpler route. Z.ai's tests show GLM-5.3 reaching a higher score than Opus 4.8 on less than half the output, and the Ed-o-meter put a full 28-task run at $0.28. Both point to a low cost per finished task, and both come with the caveats above.
If you need to run the model on your own machines, the published weights make that possible. Flash is a second option, released under the MIT license.
Check two things on the day you decide. First, latency: the Ed-o-meter measured a slower first token for GLM-5.3 than for gpt-5.5. Second, the license on the Hugging Face page, which is tagged "other" for the flagship and MIT for Flash.
FAQ
- Are the GLM 5.3 weights out yet?
- Yes. Hugging Face lists zai-org/GLM-5.3 and a BF16 build, both created on August 25, 2026. Their license tag is other, not MIT, so read the license text before you deploy. GLM-5.3-Flash is a smaller, separate model, also created on August 25, 2026, and tagged MIT.
- How does GLM 5.3 compare to Claude Opus 4.8?
- On Z.ai's own agentic coding benchmark at High effort, GLM-5.3 reaches 31.4% using around 50K output tokens, against Opus 4.8's 29.5% at 120K. That is a higher score on less than half the output. Z.ai also reports GLM-5.3 ahead of Opus 4.8 on Terminal Bench 3.0 (28.3 vs 21.1) and CyberGym (84.5 vs 78.1). All of these are vendor-run numbers.
- How does GLM 5.3 compare to Kimi K3?
- The comparison splits. Z.ai's table puts GLM-5.3 ahead on Terminal Bench 3.0 (28.3 vs 17.4), CyberGym (84.5 vs 80.0) and ExploitBench (54.4 vs 32.2). Kimi K3 leads on SWE-Marathon v1.1 (48.1 vs 42.5) and Toolathlon Verified (76.5 vs 73.0). Z.ai ran these tests itself.
- What does GLM 5.3 cost to use?
- The launch post gives points, not dollars. The GLM Coding Plan counts points separately for input, cached input and output tokens. Calls made outside peak hours use half the standard points. Peak is 14:00-18:00 UTC+8 on weekdays, so every other hour, weekends included, is billed at the half rate.
- Will my existing API calls still work?
- Not if they disable thinking. GLM-5.3 offers three effort levels, low, high and max, and no longer supports turning thinking off. Change thinking.type to enabled and set reasoning_effort to low before you switch the model ID, or the request fails.



