Skip to content

feat(zhipu): proxy GLM through an API key account - #268

Merged
caigee-cmd merged 1 commit into
mainfrom
feat/zhipu-proxy
Oct 4, 2026
Merged

caigee-cmd merged 1 commit into
mainfrom
feat/zhipu-proxy

Conversation

@caigee-cmd

Copy link
Copy Markdown
Owner

Summary

  • Add Zhipu GLM as an in-process provider. A pasted API key uses the official OpenAI-compatible endpoint, with pay-as-you-go and Coding Plan as account modes, and Coding Plan quota on the console.
  • Rewrite GLM reasoning onto the levels Zhipu accepts: older models use high/max, and glm-5.3 also accepts low.
  • Change add-account into a provider picker first. Zhipu then asks only for the account mode and API key, and form fields fill the row.

Test plan

  • go test ./...
  • Frontend typecheck via tsc -b during npm run sync
  • Add a Zhipu account from the console and send zhipu/glm-5.2
  • Confirm a Coding Plan key shows the 5-hour and weekly quota windows

Add Zhipu as an in-process provider so a pasted key can use the official pay-as-you-go or Coding Plan endpoint, and let the add-account dialog pick the provider before filling the key.
@caigee-cmd
caigee-cmd merged commit bf1f09d into main Oct 4, 2026
6 checks passed
@caigee-cmd caigee-cmd linked an issue Oct 4, 2026 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

请求添加智谱渠道反代

1 participant