The model names in this article’s original URL are now historical. Z.AI has moved its hosted coding line to GLM-5.3, so a fresh setup should use glm-5.3. The older models still matter when you maintain a pinned workflow, but they are no longer sensible defaults for a new configuration.
Current recommendation
Hosted GLM choices
| GLM-5.3 | Current default for new coding setups; text input; 1M context; reasoning always on |
|---|---|
| GLM-5.2 | Previous generation; keep only for tested compatibility |
| GLM-5.1 | Older hosted model; migrate new workflows |
| GLM-4.7 and earlier | Legacy or provider-specific availability |
| GLM-4.5-Air | Older open-weight option for local experiments |
GLM-5.3 has a 1 million-token context window and a maximum documented output of 128,000 tokens. It is a text-input model. Reasoning is always enabled, with low, high, and max effort settings available through supported APIs.
When an older model still makes sense
Keep an older model pinned when a production workflow has been tested against its exact output, a third-party host has not added GLM-5.3, or you are comparing a regression. Those are compatibility decisions, not quality recommendations.
For new work, start with GLM-5.3 and test the lowest reasoning effort that solves the task. Higher effort can help with difficult debugging, but it also increases latency and quota use.
Migration
In most clients, migration is a model-ID change:
glm-5.3
Use Z.AI’s endpoint for the protocol your client expects:
- OpenAI-compatible Coding Plan clients:
https://api.z.ai/api/coding/paas/v4 - Responses API clients:
https://api.z.ai/api/v1 - Anthropic-compatible clients:
https://api.z.ai/api/anthropic
Run a small test suite after switching. Model upgrades can change tool selection, edit style, and the amount of reasoning even when the API schema stays the same.
For setup instructions, see GLM-5.3 with Claude Code, GLM-5.3 with Codex CLI, and GLM with OpenCode.