GLM-5.2: Great Model, Shaky Coding Plan
Three days after release, developer sentiment on GLM-5.2 is split: the model's coding draws praise, but users blast the Z.ai Coding Plan's quotas.
GLM-5.2 shipped on June 13, 2026, and within three days it was on the developer community's test bench. Z.ai pushed it to the Coding Plan before any benchmark, so the first GLM-5.2 reviews were hands-on, not scores.
The GLM-5.2 reviews split cleanly: praise for GLM-5.2 coding, but the sharpest complaints aim past the model at the Z.ai Coding Plan selling it. Across Reddit, Hacker News, and X, the read is one line — good model, questionable service.
GLM-5.2's Performance in One-Shot Coding Tests
Most GLM-5.2 reviews agree it plays in a different weight class than GLM-5.1. A tester on r/ZaiGLM asked for an isometric brick-breaker — multiple input modes, difficulty select, sound effects — in a single HTML file, 'no bugs, be thorough,' and got it in one shot. The striking part came next: without running the code, the model spent minutes reviewing its own output, caught syntax errors and fixed bugs itself — about ten minutes in all.
Head-to-heads echo it. On X, one user comparison had GLM-5.2 beat Opus 4.8 in four of five identical one-shot game builds. The GLM-5.2 coding read inside agents is warm too: oh-my-opencode users say it spawns sub-agents on the first turn to scope a project, unlike GLM-5.1, and split their stack — backend on GLM-5.2, frontend planning on Kimi.
Fitting for last week's open-source release, the running cost reads low too. Some users put the GLM-5.2 coding cost about 25% below GLM-5.1, crediting better token efficiency.
Z.ai Coding Plan Quotas Draw Intense Criticism
Yet the angriest GLM-5.2 threads aren't about coding at all — they're about the Z.ai Coding Plan. On r/ZaiGLM the refrain is the GLM-5.2 quota: it reportedly burns close to 3x earlier models, users hit 'rate limit reached' after 3% of a five-hour window, and the advertised 1M context degrades past 40,000 to 80,000 tokens.
The plan's structure feeds the burn. The Z.ai Coding Plan bills per prompt, not per token, and one prompt fans into 15 to 20 model calls; with a five-hour cap and a weekly cap at once, a long agent session drains the GLM-5.2 quota fast. Hence the don't-buy-the-coding-plan posts, with even Max-tier subscribers calling it unusable after day one.
So developers separate model from service. The consensus — a strong model paired with a substandard coding plan — points to workarounds: route GLM-5.2 through an alternative API such as OpenRouter, or wait for the official standalone API and open weights due next week.
Final Verdict Awaits Next Week's Open-Source Release
This does not mean GLM-5.2 is without flaws. In the Hacker News thread 'GLM 5.2 Is Out,' users balanced praise — competitive with Claude 3.5 Sonnet on light tasks, a genuinely usable 1M context — with a warning that performance varies heavily with the prompt and the evaluation harness.
Hands-on builds reveal limits too. One developer on X tried horror games, 3D stealth games, and Minecraft clones, finding the reasoning and speed strong but core mechanics like character movement and navigation inconsistent. The model is roughly three times faster than GLM-5.1, yet its polish still trails the leading frontier models.
The consensus is plain: GLM-5.2 is a capable model, but Z.ai's official service remains the concern, and the GLM-5.2 quota gripes underline it. Three days in, most GLM-5.2 reviews rest on anecdotal cases, while the decisive part — the MIT-licensed GLM-5.2 open weights and the standalone API — is still a 'next week' promise. The real ceiling only settles once those open weights land and third parties evaluate the model on their own hosting.
