GLM Coding Plan: Why You Hit Rate Limits

You hit rate limits on the GLM Coding Plan because Z.ai never published a concurrency number to hit. Its own usage policy says the platform adjusts limits dynamically based on resource availability, ranked Max above Pro above Lite, and that is the entire published specification.

Key Takeaways:

• Concurrency is dynamic and unpublished; the docs give recommended project counts instead of limits
• Two ceilings apply at once: a 5-hour window limit and a weekly quota
• Off-peak gets you half-price points and dynamically higher concurrency, not just the discount
• Peak is 14:00 to 18:00 UTC+8 on weekdays, which is the middle of the night in the US
• Subscriptions are non-refundable even if unused, and Z.ai's two docs give different cancellation deadlines

Search the plan by name and the second organic result is a Reddit thread telling you not to buy it. Further down the same page sits a public post from someone paying $65 a month who says they get throttled too heavily to work. That gap, between a plan people keep recommending on price and a plan people keep rage-quitting on limits, is what this article is about. GLM-5.3 landed on 14 August 2026 and shipped a quota redesign alongside it, so the mechanics changed the same week.

What the GLM Coding Plan actually includes

Three tiers, all of which now serve GLM-5.3 after Z.ai rolled it out to every subscriber at launch. List pricing as of 14 August 2026, before the discounts that quarterly and yearly billing carry:

Longer commitments discount that: quarterly takes 20% off and yearly 30%, which is where the $12.60 Lite figure floating around comes from. All three tiers work inside more than twenty agents, Claude Code, OpenCode, Cline, Kilo Code and OpenClaw among them, and all three bundle the same MCP set for vision, web search, web reading and Zread.

Notice that Z.ai describes tiers by repo size rather than by request count. That's not marketing vagueness; it follows directly from how the limits work.

The rate limit nobody publishes

Here's the sentence that explains most of the complaints, taken from the GLM Coding Plan usage policy: rate and concurrency limits are tied to your tier, and "the platform dynamically adjusts these limits based on resource availability, with the general principle being Max > Pro > Lite."

There's no number. Not a requests-per-minute figure, not a concurrent-session cap, nothing you could design around. What the docs offer instead is a recommendation in units of projects:

• Lite: one project at a time
• Pro: one or two simultaneously
• Max: two or more

So when someone on Pro fires up four agent sessions and watches three of them stall, the plan is behaving as documented. It just isn't behaving as sold, because "6x Lite usage" reads like a throughput promise and functions as a budget. Z.ai's own FAQ carries a question titled roughly "why does it sometimes feel like there's only one concurrent connection", which tells you how often this comes up.

Two ceilings apply at the same time, and mixing them up is the second most common confusion: a 5-hour rolling window limit, and a weekly quota. Burning your week in two days is possible on any tier. So is sitting well under your weekly quota and still getting throttled inside a single afternoon.

The points quota, and the peak hours that decide what it costs

The launch of GLM-5.3 came with a new billing mechanic. The plan now runs on points, counted separately for input, cached input and output tokens, and calls made outside peak hours consume half the standard points. Peak means 14:00 to 18:00 UTC+8, Monday through Friday; every other hour, weekends included, bills at the off-peak rate.

Convert that timezone before you plan anything around it. Those four peak hours are 02:00 to 06:00 US Eastern and 07:00 to 11:00 UK time, which produces a genuinely odd split:

If you're in the US, you were quietly handed a 50% discount on your entire workday and most people haven't noticed. If you're in China, your most expensive four hours are the ones right after lunch.

Off-peak buys more than a discount

This is the part worth knowing, and it's one line in the usage policy that nobody quotes: "Plan users will enjoy higher concurrency limits during off-peak hours (dynamically increased), enabling support for a greater number of concurrent projects."

So off-peak isn't only cheaper. It's also the window where the unpublished concurrency ceiling goes up, which means the two problems people complain about most, cost and throttling, have the same fix and it's a clock rather than an upgrade. Someone on Lite running a batch at 3am UTC+8 may get more parallel work through than the same account managing two projects at 3pm.

Max tier gets a related perk phrased from the other direction, "dedicated resources during peak times", which is really Z.ai selling you an exemption from the queue you'd otherwise sit in.

What error 1113 actually means

Z.ai's FAQ has an entry for 1113 Insufficient Balance turning up after someone bought a coding package, and the answer isn't the one most people assume. Running out of plan quota does not fall through to your account balance. Calls from supported tools draw on the plan and nothing else, and when the quota's gone you wait for the next 5-hour refresh; the plan FAQ says so in as many words.

1113 means your setup didn't qualify as plan usage in the first place. Three conditions have to hold together:

• The tool has to be on the officially supported list
• The base URL has to match, and it differs by tool: Claude Code and Goose point at https://api.z.ai/api/anthropic, everything else at https://api.z.ai/api/coding/paas/v4
• The model has to be GLM-5.3, GLM-5-Turbo or GLM-4.7, the only three the plan serves

The base URL catches the most people, because getting it wrong in a way the client still accepts surfaces as a billing error rather than a connection error, and nobody debugs a billing error by checking their endpoint. Worth knowing too: GLM-5.2 isn't on the plan's model list at all. A config still pinned to it fails the third condition even though the model obviously exists and worked last month.

Non-refundable, and two different cancellation deadlines

Refunds don't exist here. Both the usage policy and the FAQ state that a purchased subscription is confirmed and non-refundable even when it goes unused, with no proration and no credit for what you didn't spend.

The cancellation deadline is genuinely unsettled, because Z.ai's own two pages disagree. The usage policy says cancel at least 3 days before your next billing date; the FAQ says at least 24 hours. Go with 3 days until one of them changes, since being early costs nothing and being late costs a full non-refundable cycle.

Upgrades hide a trap of their own. Moving to a longer billing cycle at the same tier, Lite monthly to Lite annual for instance, does not take effect when you pay for it. The new plan queues behind the current one and the validity periods stack, which Z.ai illustrates with a 13-month example. Only cross-tier upgrades activate immediately, converting what's left of the old plan into balance pro rata to offset the difference.

All of which argues for starting on Lite monthly instead of reaching for the 30% yearly saving. The discount is real; so is the fact that a yearly Max subscription is $1,176 you can't get back if the model stops fitting your work in October.

There's a risk-control layer to read once, as well. Account sharing is prohibited, use outside supported tools can restrict benefits, and accounts passing three violations may be banned outright, with appeals going through the console.

Which tier fits which repo, honestly

For most individuals the answer is Lite, and I'd argue that harder than Z.ai's page does. Ten thousand credits a week against a small repo, on a plan where your working hours are probably off-peak anyway, covers a lot before the ceiling shows up. Start there and let the throttling tell you when to move.

Pro earns its keep at the point you genuinely run two agent sessions at once, not when you merely want to. Max is for people billing clients while it runs, where the peak-hour exemption is the actual product and the quota is incidental.

What none of the tiers fix is the shape of the work. Z.ai trained GLM-5.3 on tasks it describes as several days of work for an experienced engineer, and the launch post leans on long-horizon delivery as the headline capability. A quota tier decides how much of that you can buy. It doesn't decide whether there's a machine still running when the job's three hours in and your laptop lid is shut. Cline's write-up on pairing Z.ai models with an agent makes the same point from the tooling side, and we covered the general version in what an always-on AI agent actually requires.

Getting more out of a GLM Coding Plan subscription

Move the heavy work off peak, and mean it literally: schedule it rather than deciding hour by hour, because the win is a doubled point budget plus a concurrency bump you can't otherwise buy. Keep every call inside the officially supported tools so nothing quietly bills against your balance. Start monthly, upgrade on evidence, and treat the yearly discount as a decision you make in month three.

The plan is genuinely cheap for what it serves, which is why the complaints read as betrayal rather than disappointment; people expected throughput and bought a budget. Read it as a budget from the start and it stops being a bad deal. GLM-5.3 is only reachable through this plan right now anyway, since the public API hasn't opened, so for the next couple of weeks the subscription is the model.

MoClaw sits beside that rather than against it: a hosted cloud AI computer that keeps running when your machine doesn't, which is what turns a 3am off-peak window into something you can actually use. The free trial runs three days on 1,000 credits, and a $20 subscription carries 1,000 credits a month.

FAQ

Why do I get rate limited on the GLM Coding Plan?

Because concurrency limits are dynamic and unpublished. Z.ai's usage policy says the platform adjusts them based on resource availability, ordered Max > Pro > Lite, and recommends one project at a time on Lite, one or two on Pro, and two or more on Max. Two separate ceilings also apply together: a 5-hour window limit and a weekly quota.

What are GLM Coding Plan peak hours?

14:00 to 18:00 UTC+8, Monday to Friday. Everything else, weekends included, is off-peak and consumes half the points. In US Eastern time the peak window is 02:00 to 06:00, so a US working day sits entirely in off-peak.

How much does the GLM Coding Plan cost?

List pricing on 14 August 2026 is $18 a month for Lite, $80 for Pro and $168 for Max, with roughly 20% off quarterly billing and 30% off yearly. Lite includes 10,000 credits per week; Pro and Max are described as 6x and 14x that.

Can I get a refund on the GLM Coding Plan?

No. Both the usage policy and the plan FAQ state that a purchased subscription is confirmed and refunds are not supported, including when the plan goes unused. To stop the next cycle you have to cancel ahead of the billing date, though the two pages disagree on how far ahead: the usage policy says 3 days and the FAQ says 24 hours. Use 3 days.

Does the GLM Coding Plan include GLM-5.3?

Yes. Z.ai rolled GLM-5.3 out to all GLM Coding Plan subscribers on launch day, 14 August 2026, across all three tiers. The public API for the model had not opened at that point.

Why do I get error 1113 Insufficient Balance with an active subscription?

Because the call didn't qualify as plan usage. Z.ai requires three things together: an officially supported tool, the correct base URL for it (https://api.z.ai/api/anthropic for Claude Code and Goose, https://api.z.ai/api/coding/paas/v4 for everything else), and one of the three models the plan serves, GLM-5.3, GLM-5-Turbo or GLM-4.7. Exhausting your quota inside a supported tool does not cause this and does not touch your balance; you just wait for the next 5-hour refresh.

Pricing, quota terms, rate-limit language, error conditions and refund policy in this article were read off Z.ai's subscription page, its GLM Coding Plan usage policy and its plan FAQ on 14 August 2026, and the cancellation-window contradiction between those last two was present on that date. The points system launched the same day as GLM-5.3 and the discounts are promotional, so check current terms before subscribing.