- Date: 2026-08-14
- Type: feature
- Scope:
glm5_3,glm5_1,glm5_2,auto_client,registry - PR: #169
AgentHub now supports Z.AI/Zhipu's glm-5.3 (announced at https://z.ai/blog/glm-5.3), and
the GLM series clients merge into one, following the Gemini unification: glm5_1/ and
glm5_2/ fold into a single glm5_3/ client per language, named for the newest
generation. Outside the thinking parameter contract the 5.1 and 5.2 implementations
differed only by the reasoning_effort mapping, so per-generation rules now live in one
client.
- Docs-only implementation. The GLM-5.3 API was announced but not live at the time
of this change, so there is no live capture; the implementation follows the official
pre-launch documentation at docs.bigmodel.cn, snapshotted under
llmsdk_docs/glm5_3/.glm-5.2stays as the env-gated E2E model until the API is live. - Per the docs, GLM-5.3 keeps the GLM-5.2 wire format (1M context, 128K max output,
streaming
reasoning_content/content/tool_calls,tool_stream,tool_choiceautoonly) and changes only the thinking contract:- GLM-5.3 uses forced thinking and errors on
thinking.type: "disabled", soThinkingLevel.NONEdegrades to the new light-reasoningloweffort with thinking enabled. - GLM-5.3 accepts only
low/high/maxforreasoning_effortand errors on other values, so the client clamps:LOW→low,MEDIUM/HIGH→high,XHIGH→max. GLM-5.2 keeps the full pass-through vocabulary (the server maps it), and pre-5.2 models still send noreasoning_effortat all.
- GLM-5.3 uses forced thinking and errors on
- Routing folds to the
glm-5prefix, which every previously accepted GLM client type contains, soglm-5.1/glm-5.2spellings keep working; the supported-types message listsglm-5.3first. Official registry entries were repointed atglm-5.3; the OpenRouter-hostedz-ai/glm-5.2entry was not changed.
glm-5.3 is registered with text input/output and a 1,000,000-token context window.
Pricing is omitted: the API is not yet live and Z.AI publishes no GLM-5.3 price at
snapshot time.