[Feature] Add glm-5.3 to the z.ai coding plan catalog #1444
Closed
Kenmege
started this conversation in
Feature requests
Replies: 3 comments
|
Hey @Kenmege Meanwhile you can use this gist to add the model as a custom model https://gist.github.com/i3130002/95804339b51a09660c742ec12af3fc1c |
0 replies
|
Live verification on the coding plan, in case it helps the decision: with the 18-line entry applied on top of current |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Problem
z.ai has served
glm-5.3on the Z.AI Coding Plan endpoint since 2026-08-14, but Prime Agent'szaicatalog tops out atglm-5.2. The registry is explicit rather than fetched (thegenerate-models.tssnapshot), so the model does not exist for model selection orfind_models().Evidence
GET https://api.z.ai/api/coding/paas/v4/modelswith a coding-plan key listsglm-5.3alongsideglm-5.2(created2026-08-14).zai-coding-plancatalog listsglm-5.3: 1M context / 131072 output, effort levels low/high/max, tool calls on.Proposed change
Regenerate the snapshot (
npm run generate-modelsinpackages/ai) and scope the diff to thezaisection — same shape as #1247: an 18-line addition topackages/ai/src/models.generated.tsmirroring theglm-5.2entry (coding-plan baseUrl,zaiToolStream,thinkingFormat: "zai"; models.dev lists no per-token pricing for the plan, so cost stays0like its siblings).Ready branch
Validated on
Kenmege/prime-agentbranchfeat/zai-glm-5.3(branched from currentmain, one commit, +18 lines):npm run checkclean from the repo root (biome 915 files,tsgo --noEmit, installer render, browser smoke). I opened #1443 before noticing the vouching policy in CONTRIBUTING — it was auto-closed as expected for an unvouched author. Happy to re-open it, rebase, or hand the commit to a maintainer, whichever is easiest; if someone is willing to vouch, the branch is push-button ready.All reactions