AI DevelopmentCoding

GLM-5.3 in 2026: Benchmarks, Pricing and Setup Guide

September 3, 2026
10 min read
GLM-5.3 in 2026 benchmarks, pricing and setup guide
Share:

If you write code with AI in 2026, the name to know is GLM-5.3 from Zhipu (Z.ai). Launched August 14, 2026 on the same base model as GLM-5.2 — every gain comes from post-training alone — it is now the open-weights coding flagship: open-source SOTA on Terminal-Bench 3.0 and Agents’ Last Exam, 84.5% on CyberGym, and open weights on Hugging Face since late August.

In this guide I show you the exact spec sheet of GLM-5.3, its public benchmark numbers against GLM-5.2 and the closed frontier (all Z.ai-reported, sources at the end), what changed since GLM-5.2, and how to run it today in Claude Code, Cline, or with the raw API.

1. GLM-5.3 at a Glance: the Spec Sheet

GLM-5.3 is the August 2026 flagship of Zhipu’s GLM-5 family, and the model with the most complete public benchmark sheet of the whole GLM line. Same 744B-class MoE base as GLM-5.2, roughly 40B active per token — no new pretraining, just a scaled post-training run. Open weights landed on Hugging Face (zai-org/GLM-5.3) in late August after a two-week safety review, and every figure below is a public GLM-5.3 number with its source at the end of the article.

Parameters

Same 744B-class MoE base as GLM-5.2, ~40B active (post-training only)

Context

1M tokens (1,048,576), 128K max output, text-only

License

Open weights — Hugging Face zai-org/GLM-5.3

API price

$1.40 / 1M input, $4.40 / 1M output tokens

Coding Plan

Lite from ~$18/mo, Pro and Max tiers for heavy use

Where it runs

Claude Code, Cline, Kilo Code, Roo Code, OpenClaw + API

Lighter sibling

GLM-5.3-Flash (Aug 26): 320B/18B multimodal, MIT, $0.15/$0.50 per 1M

Why the 1M context matters

Most coding models advertise long context but degrade after a few hundred thousand tokens. GLM-5.3’s headline feature is a solid 1M-token window that holds up on multi-hour agentic tasks — that is exactly what the Terminal-Bench 3.0 and DeepSWE scores below are measuring.

The lineage is short and fast: GLM-4.5 (355B, July 2025) → GLM-4.6 (200K context, September 2025) → GLM-4.7 (December 2025) → GLM-5 (744B, February 2026) → GLM-5.1 (April 2026) → GLM-5.2 (June 2026, the verified anchor: 62.1 SWE-bench Pro, 81.0 Terminal-Bench 2.1) → GLM-5.3 (August 2026). Twelve days later Z.ai added GLM-5.3-Flash: a different, newly trained 320B/18B natively multimodal model (image + video in) that beats GLM-5.2 at roughly one-tenth the API price.

2. What Improved vs GLM-5.2

One fact frames everything: GLM-5.3 reuses GLM-5.2’s base model, so every point below comes from post-training on scaled, executable, verifiable environments. The jumps are large precisely where tasks look like real engineering work. Here is GLM-5.3 against GLM-5.2 and the closed frontier — all Z.ai-reported figures from the official docs and launch blog:

28.3

Terminal-Bench 3.0

Up from 4.6 on GLM-5.2; open-source SOTA per Z.ai, ahead of the previous open field.

66.9

DeepSWE v1.1

Up from 46.2 on GLM-5.2 — a ~45% jump from post-training alone.

28.5

Agents’ Last Exam

Up from 23.8 on GLM-5.2; open-source SOTA on agentic CLI tasks per Z.ai.

84.5%

CyberGym

Up from 77.2% on GLM-5.2; best on the benchmark, ahead of Mythos 5 (83.8%) and GPT-5.6 Sol (83.6%).

54.4%

ExploitBench

More than double GLM-5.2’s 24.4%; still trails Mythos 5 (78.0%) and GPT-5.6 Sol (76.5%).

+50%

Z.ai Code Bench (in-house)

Private realistic-agent benchmark vs GLM-5.2; at Max effort 34.5% completion at ~75K tokens vs 23.4% at ~96K.

The number that convinced me

Terminal-Bench 3.0 going from 4.6 to 28.3 without a new base model is the difference between a benchmark curiosity and a model you can hand a terminal to. DeepSWE 46.2 to 66.9 tells the same story on long-horizon work — treat it as “post-training is the new pretraining”, not as a final verdict over the closed frontier.

For reference, GLM-5.2 remains the verified anchor on the older suites: 62.1 on SWE-bench Pro (beating GPT-5.5’s 58.6, trailing Claude Opus 4.8’s 69.2) and 81.0 on Terminal-Bench 2.1. The GLM-5.3 era moved the line to harder suites — Terminal-Bench 3.0, DeepSWE, Agents’ Last Exam, CyberGym — which is why you should compare 5.3 against 5.2 on the same benchmark, never across different ones.

3. Quickstart: Claude Code, Cline, and Raw API

You have three verified paths to run GLM-5.3 today: the GLM Coding Plan inside Claude Code, any OpenAI-compatible tool like Cline, or the raw Z.ai API with model id glm-5.3. Pick the one that matches your setup — all three endpoint URLs below come straight from the official docs.

Option A — Claude Code (Anthropic protocol)

Install Claude Code, create a Z.ai API key, then point Claude Code at the Coding endpoint in ~/.claude/settings.json. This exact shape is the documented GLM-5.3 recipe:

npm install -g @anthropic-ai/claude-code

// ~/.claude/settings.json
{
  "env": {
    "ANTHROPIC_AUTH_TOKEN": "your_zai_api_key",
    "ANTHROPIC_BASE_URL": "https://api.z.ai/api/anthropic",
    "ANTHROPIC_DEFAULT_SONNET_MODEL": "glm-5.3[1m]",
    "ANTHROPIC_DEFAULT_OPUS_MODEL": "glm-5.3[1m]",
    "CLAUDE_CODE_AUTO_COMPACT_WINDOW": "1000000",
    "API_TIMEOUT_MS": "3000000"
  }
}

cd your-project-directory
claude

Option B — Cline (OpenAI-compatible protocol)

In Cline choose “Use your own API Key” with provider OpenAI Compatible, base URL https://api.z.ai/api/coding/paas/v4, model glm-5.3, uncheck Support Images (GLM-5.3 is text-only), and set the context window to 1000000. That is the documented Cline recipe, verified in the Z.ai devpack docs.

Provider:  OpenAI Compatible
Base URL:  https://api.z.ai/api/coding/paas/v4
API Key:   your_zai_api_key
Model:     glm-5.3  (custom model name)
Images:    OFF (uncheck Support Images, GLM-5.3 is text-only)
Context:   1000000

Option C — Raw API with the OpenAI Python SDK

For scripts and custom harnesses, the general endpoint https://api.z.ai/api/paas/v4/ speaks the OpenAI chat-completions protocol. Minimal working call with reasoning enabled (required for GLM-5.3):

pip install --upgrade "openai>=1.0"

from openai import OpenAI

client = OpenAI(
    api_key="your-Z.AI-api-key",
    base_url="https://api.z.ai/api/paas/v4/",
)

completion = client.chat.completions.create(
    model="glm-5.3",
    messages=[
        {"role": "system", "content": "You are a senior backend engineer."},
        {"role": "user", "content": "Refactor this function for clarity and add tests."},
    ],
    extra_body={
        "thinking": {"type": "enabled"},
        "reasoning_effort": "max",  # low | high | max (default max)
    },
)
print(completion.choices[0].message.content)

Tip: thinking is mandatory, [1m] unlocks full context

GLM-5.3 always runs with reasoning enabled — thinking.type must be enabled and disabling it fails the request; use reasoning_effort low, high, or max (max for hard coding tasks). In Claude Code, append [1m] to the model name (glm-5.3[1m]) and set CLAUDE_CODE_AUTO_COMPACT_WINDOW to 1000000 to unlock the full 1M window.

Heads-up on endpoints: the Coding Plan quota only works on the coding endpoints (Anthropic https://api.z.ai/api/anthropic or OpenAI https://api.z.ai/api/coding/paas/v4). Pointing your tool at the general endpoint bills differently and does not consume plan quota. Need vision or a cheaper tier? That is GLM-5.3-Flash territory (natively multimodal, $0.15/$0.50 per 1M) — not this flagship.

4. Honest Limits

GLM-5.3 is the strongest open-weights coding model I have tested this year, but “strongest open” is not “best at everything”. Here is where it still loses, so you can decide with clear eyes.

⚠️

Still trails the closed frontier on exploitation

ExploitBench 54.4% vs Mythos 5 at 78.0% and GPT-5.6 Sol at 76.5%; ExploitGym 105/130 vs Mythos 5’s 181/247. The further up the exploitation chain, the wider the remaining gap.

⚠️

All launch numbers are vendor-reported

Z.ai publishes methods and some trajectories, but these are first-party runs. Re-run the two benchmarks that match your workload before migrating a team.

⚠️

Text-only — no vision

GLM-5.3 takes text in, period. If your workflow needs screenshots, diagrams, or video, that is GLM-5.3-Flash (natively multimodal) instead.

⚠️

Thinking cannot be turned off

Reasoning is always enabled; thinking.type disabled fails the request. You only get the reasoning_effort dial (low/high/max) — budget latency and tokens accordingly.

⚠️

Self-hosting 744B-class weights is not a weekend project

Open weights do not mean a laptop model. You need a multi-GPU cluster with vLLM or SGLang — for most teams the hosted API or the Coding Plan is the sane path; Flash’s 320B MIT weights are the lighter self-host option.

The most common mistake

Mixing up the two SKUs. GLM-5.3 is the text-only coding and cyber-defense flagship; GLM-5.3-Flash is a different, newly trained 320B/18B multimodal model at one-tenth the price. Pick the flagship for maximum coding capability, Flash for vision and cost.

None of these limits is a dealbreaker — they are the normal price of open weights at the frontier. The cost math (same $1.40/$4.40 per 1M as GLM-5.2, Flash at one-tenth of that) leaves generous room to run your own evals before committing.

Verdict

If you want frontier-adjacent coding without frontier pricing, GLM-5.3 is the default open-weights answer in September 2026: 28.3 on Terminal-Bench 3.0, 66.9 on DeepSWE, 28.5 on Agents’ Last Exam, 84.5% on CyberGym, a real 1M context, open weights, and first-class support in Claude Code and Cline — with GLM-5.2’s 62.1 SWE-bench Pro sheet as the verified fallback.

My recommendation: start with the Coding Plan Lite tier on a real repo for two weeks with model glm-5.3 (reasoning_effort max), keep GLM-5.2 as your baseline, and compare completed tasks — not benchmark screenshots. If it holds up, scale to Pro; reach for GLM-5.3-Flash when you need vision or one-tenth the per-token cost.

Bottom line

Use it for

  • • Agentic coding in Claude Code
  • • Terminal-heavy long-horizon tasks
  • • Vulnerability discovery assist

Skip it for

  • • Vision/multimodal workflows
  • • Unsupported toolchains
  • • Offensive-security expectations

Remember

  • • Thinking stays enabled
  • • [1m] unlocks full context
  • • Verify on your workload

Sources

Diego Rodriguez

Diego Rodriguez

Senior Full-Stack & AI Engineer

Diego has 10+ years of experience building production-grade AI-powered applications, from LLM orchestration and RAG pipelines to ML-driven risk detection and algorithmic trading systems.

Learn more about Diego →