Greptile Summary

This PR updates the CLI setup documentation for the GLM and Z.AI providers (in both English and Chinese) to replace the single generic --auth-choice zai-api-key command with four granular auth choices (zai-global, zai-coding-global, zai-coding-cn, zai-cn), which match the current implementation in src/commands/auth-choice-options.ts. It also adds glm-5 to the list of example model IDs in the GLM notes.

Key observations:

• All four new --auth-choice values are valid and confirmed in src/commands/auth-choice-options.ts (line 114).
• The non-interactive --zai-api-key "$ZAI_API_KEY" example was removed from docs/providers/zai.md; the underlying --zai-api-key <key> flag is still present in the code but is no longer documented — this is a minor documentation regression for users who rely on non-interactive/scripted setup.
• The Chinese translations (docs/zh-CN/providers/glm.md and docs/zh-CN/providers/zai.md) have the CLI section correctly updated, but their config snippets and example model IDs still reference zai/glm-4.7 instead of zai/glm-5, inconsistent with the English source. This affects the intro sentence of zh-CN/providers/glm.md (line 18), the config snippet in both zh-CN files (line 41 each), and the Notes example in zh-CN/providers/zai.md (line 47).

Confidence Score: 4/5

• Safe to merge; docs-only change with no runtime impact, but the Chinese translations have minor model-ID inconsistencies worth cleaning up.
• All new auth choice values are verified against the live implementation. The only issues are cosmetic inconsistencies in the Chinese translations (stale glm-4.7 references in config snippets and example text where glm-5 is now the preferred default), and the undocumented removal of the non-interactive --zai-api-key example. Neither affects correctness or runtime behaviour.
• docs/zh-CN/providers/glm.md and docs/zh-CN/providers/zai.md — config snippets and example model IDs are out of sync with the English sources.

_{Last reviewed commit: 33925f4}

I think the Z.AI endpoint choices are getting conflated here:

• zai-global is the explicit general API endpoint, not the Coding Plan endpoint.
• zai-api-key is the current default smart path in OpenClaw: it auto-detects the working endpoint for the key and prefers general glm-5 when available.
• If the goal of this doc update is "use your existing monthly Coding Plan instead of pay-as-you-go API billing", the explicit command should be zai-coding-global, not zai-global.

So I think we should either keep zai-api-key as the primary example, or explicitly recommend zai-coding-global for Coding Plan users.

hi @obviyus thanks for your suggestion. Since the endpoint returned by zai-api-key can be uncertain, users cannot clearly know which actual endpoint their requests are being routed to. Therefore, I have removed it from the documentation. I’ll update the doc to recommend zai-coding-global for Coding Plan users.

@obviyus PTAL thanks.
Btw, I will submit a new model pr tomorrow that has been optimized for our openclaw. Could you help take a review if have time? I would really appreciate it.

Opened #45969 to supersede this one.

That follow-up carries the same docs update, but also fixes the runtime path so explicit zai-coding-* onboarding choices still detect and set a working default model (glm-5 when available on the chosen endpoint, otherwise glm-4.7).

Opened #45969 to supersede this one.

That follow-up carries the same docs update, but also fixes the runtime path so explicit zai-coding-* onboarding choices still detect and set a working default model (glm-5 when available on the chosen endpoint, otherwise glm-4.7).

git it, thanks