As of June 14, 2026, Z.AI’s official Coding Plan documentation shows GLM-5.2 as available for Coding Plan users, with setup guidance for Claude Code, OpenClaw, Cline, and other supported coding tools. That makes this a real model-release story for engineering teams, because the upgrade is not only a new model name: the docs now describe a 1M-context configuration, an OpenAI-compatible coding endpoint path, and updated quota guidance that materially changes how teams should evaluate long-horizon coding agents.
Zhipu also told IT之家 on June 13 that GLM-5.2 would open to all GLM Coding Plan users that evening, with API availability and an MIT open-source release planned for the following week. The key caveat is that public source material is still much stronger on configuration and rollout than on third-party benchmarks, so teams should avoid treating GLM-5.2 as a fully benchmarked default until more official performance material lands.
What changed from GLM-5.1
The most concrete change is context. Z.AI’s earlier GLM-5.1 Coding Plan guidance described a 200,000-token context setting in other tools and a 204,800 context window in OpenClaw configuration examples. The new GLM-5.2 switching guide instead shows a 1,000,000-token setup path, including the glm-5.2[1m] suffix for Claude Code and a 1,000,000 context window for OpenClaw and Cline-style configurations.
That does not automatically mean every long-context task will improve. It does mean Z.AI is now officially positioning GLM-5.2 for much larger repo state, longer agent traces, and broader working memory inside coding-agent loops than the documented GLM-5.1 setup supported.
- GLM-5.1 documented baseline: 200K to 204.8K context in Coding Plan integration docs.
- GLM-5.2 documented path: 1M context when configured with the model suffix and matching window settings where supported.
- Effort guidance changed too: Z.AI now explicitly recommends max effort for harder coding tasks, rather than treating the model as a simple drop-in replacement.
How GLM-5.2 plugs into coding-agent tools
The rollout matters because it is not confined to a first-party chat surface. Z.AI’s tool-integration docs say the GLM Coding Plan supports both an OpenAI Chat Completions protocol endpoint and an Anthropic Messages endpoint, depending on the coding tool.
For OpenAI-compatible tools such as Cline and similar custom-model workflows, the relevant path is the dedicated coding endpoint rather than a generic public chat route. In practice, that means teams can test GLM-5.2 inside existing coding-agent shells instead of waiting for a separate product launch.
- Claude Code / Goose-style path: Z.AI documents the Anthropic-compatible endpoint for those tools.
- Cline and similar tools: Z.AI documents an OpenAI-compatible setup using the coding endpoint and a custom glm-5.2 model entry.
- OpenClaw: The latest guide now shows a direct zai/glm-5.2 configuration with a 1,000,000 context window.
That is the operational story: GLM-5.2 is not just available in theory. Z.AI is documenting how to wire it into real coding-agent environments.
The quota story improved, but it is not automatically cheap
Teams moving from GLM-5.1 should pay close attention to the economics. Z.AI’s FAQ still classifies GLM-5.2 as an advanced model with premium quota consumption: 3× the standard rate during peak hours and 2× during off-peak hours. The good news is that the docs now say GLM-5.2 and GLM-5-Turbo will consume only 1× quota during off-peak hours through the end of September.
That matters versus the earlier GLM-5.1 wording, which offered the same 1× off-peak treatment only through the end of June. In other words, the new story is not that GLM-5.2 is fundamentally cheaper than GLM-5.1 under normal conditions. The more defensible read is that Z.AI has extended a favorable off-peak incentive window while pushing a more capable long-context model into the Coding Plan.
The underlying plan buckets themselves are unchanged in the FAQ:
- Lite: up to about 80 prompts every 5 hours.
- Pro: up to about 400 prompts every 5 hours.
- Max: up to about 1600 prompts every 5 hours.
If a team exhausts quota, the plan refreshes on the next 5-hour cycle and supported-tool calls do not automatically spill into account-balance charges. For migration planning, that makes GLM-5.2 easier to sandbox, but it does not remove the need to measure quota burn on real repos.
What teams should test before moving long-horizon coding agents
The biggest mistake would be reading “1M context” as “safe to promote everywhere.” A better approach is to treat GLM-5.2 as a serious candidate for deeper coding-agent work and then run focused tests against the failure modes that actually matter.
- Context compression and recall: Verify whether the agent still retrieves the right files, decisions, and earlier steps late in a long session instead of just holding more tokens in theory.
- Tool-call stability: Test file edits, shell actions, retry behavior, and long-running multi-step execution through the documented coding endpoint, not only short prompt-response tasks.
- Effort-mode tradeoffs: Compare default/high behavior against max effort on difficult refactors, repo-wide debugging, and stubborn build failures to see whether the extra reasoning is worth the latency and quota cost.
- Quota burn versus fallback policy: Measure whether GLM-5.2 should be reserved for planning, repo-wide debugging, and complex merge work while GLM-4.7 handles routine edits and daily implementation.
- Long-session drift: Check whether the model stays aligned with repo conventions, test strategy, and prior decisions over extended agent runs instead of slowly rewriting assumptions midstream.
What to watch next
The near-term watch items are straightforward. First, teams should look for official public material that goes beyond setup docs: benchmark disclosures, a fuller standalone GLM-5.2 model page, and clearer public API rollout details. Second, they should watch whether Z.AI keeps the current off-peak quota incentives in place once the initial adoption push passes.
For now, the safest conclusion is that GLM-5.2 is a real June 2026 upgrade for coding-agent teams because the official docs now support it operationally. But the evidence base is still stronger on availability, context configuration, endpoint setup, and quota policy than on independent head-to-head proof. For businesses building AI agents, that means GLM-5.2 is worth testing immediately for long-horizon engineering workflows, but it should earn production default status through evals, not hype.