Skip to content

[til] til: GLM-5.3 Review: Z.ai's New Open Weights Model for Coding and Agentic Workflows - #76

Merged
sameerkhansf merged 2 commits into
mainfrom
til/glm-5-3-review-2026-5aac23add4268d39
Sep 4, 2026
Merged

sameerkhansf merged 2 commits into
mainfrom
til/glm-5-3-review-2026-5aac23add4268d39

Conversation

@github-actions

@github-actions github-actions Bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

Angle Chosen

GLM-5.3 Review: Z.ai's New Open Weights Model for Coding and Agentic Workflows

This topic was selected because GLM-5.3 represents a significant release in the open weights LLM space, showing strong performance on coding and agentic benchmarks. The model builds on GLM-5.2 with extensive post-training improvements, demonstrating emergent capabilities in cybersecurity tasks and competitive performance on coding benchmarks. This fills a gap in the site's coverage of recent open weights models focused on agentic workflows.

Evidence Summary

Key factual claims extracted from sources:

  • GLM-5.3 uses same base model as GLM-5.2 with gains from post-training
  • 50% improvement over GLM-5.2 on Z.ai Code Bench
  • Terminal Bench 3.0: 28.3 (vs GLM-5.2 4.6)
  • CyberGym: 84.5 (vs GLM-5.2 77.2)
  • ExploitGym (2h/6h): 105/130 (vs GLM-5.2 29/39)
  • Agents' Last Exam: 28.5 (vs GLM-5.2 23.8)
  • GDPval-AA v2: 1769 (vs GLM-5.2 1508)
  • DeepSWE (v1.1): 66.9 (vs GLM-5.2 46.2)
  • NL2Repo: 58.0 (vs GLM-5.2 48.9)
  • Toolathlon Verified: 73.0 (vs GLM-5.2 59.9)
  • AutomationBench (v1.0.6): 48.2 (vs GLM-5.2 26.2)
  • HLE w/ Tools: 62.5 (vs GLM-5.2 54.7)
  • Context length: 300K tokens with context management strategy
  • Reasoning effort parameter: low, high, max (defaults to max)
  • Deployment compatible with SGLang, vLLM, TokenSpeed, Transformers, KTransformers, Unsloth, Ascend NPU

Verification Checklist

  • All numbers and factual claims trace to sources fetched this run
  • No personal testing claims ("I tested", "in my testing" avoided)
  • Every table row includes source links for numeric values
  • Title follows format: "X Review: (specific angle)"
  • Description is one-sentence summary of verdict/scope
  • Frontmatter values properly quoted (title, description, date)
  • Tables use proper pipe spacing (| Model | Price | not |Model|Price|)
  • No emoji used in headings, tables, lists, or body
  • No unsupported superlatives or clickbait in title
  • Post length targets 800-2000 words (current ~1200)
  • Slug (glm-5-3-review-2026) does not collide with existing slugs
  • Category is existing category: AI
  • Published set to true in frontmatter
  • Author set to Sameer Khan
  • Tags included (3-6 items)

Generated by Daily TIL Scout · ⊞ 32.9K ·

@vercel

vercel Bot commented Sep 3, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
sameer-khan Ready Ready Preview Sep 3, 2026 11:51pm UTC

@sameerkhansf
sameerkhansf marked this pull request as ready for review September 4, 2026 17:51
@sameerkhansf
sameerkhansf merged commit 5dadfd4 into main Sep 4, 2026
6 checks passed
@sameerkhansf
sameerkhansf deleted the til/glm-5-3-review-2026-5aac23add4268d39 branch September 4, 2026 17:51
sameerkhansf added a commit that referenced this pull request Sep 8, 2026
Run 34261048698 was the first run to reach the post-writing path since #76 —
the gate correctly printed CLEAR — and it failed on the invocation cap:

  attempt 1: 56 turns / 93 invocations, then
             "Upstream error from Nvidia: Service temporarily overloaded"
             (transient, classified partial_execution, budget remaining)
  attempt 2: harness restarts the session from scratch, dies on
             "429 Maximum LLM invocations exceeded (120 / 120)"

max-turns is not only a turn count: it is the AWF api-proxy's hard per-run LLM
invocation cap, and that budget is pooled across every harness retry attempt
(github/gh-aw#52836, #45827). At 120 a single pass fits and a retry cannot, so
any transient upstream blip on the free NVIDIA endpoint kills the run. 250
leaves room for one full pass plus a retry.

This is a symptom fix with a known ceiling. gh aw audit has flagged
"about 50% of this run's turns appear to be data-gathering that could move to
deterministic steps" on every run, and the log shows the cause: repeated
`curl <hf-readme> | grep -i "parameters|context|license|price"` against the
same files. Pre-fetching candidate READMEs in the `steps:` block is the
DeterministicOps fix and the next lever if the cap is hit again.


Claude-Session: https://claude.ai/code/session_01Vru5xPN55JPU7dyVS3uswd

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant