zai-org / zai-org/feedback

[Bug] Z.ai API persistent "Connecting" hang in ZCode 3.1.4 — entitlement endpoint fails, model returns HTTP 529

Open
#43 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

priority: P2 status: 待评估 type: Bug
Dominant language
No language data
Stars
22
Forks
1
PR merge metrics
No merged PRs in 30d

Description

提交前确认 · Pre-submission checklist
  • 我已搜索过现有 issue,确认这不是重复 / I searched existing issues and confirmed this isn't a duplicate.
  • 我已阅读 CONTRIBUTING.md / I've read CONTRIBUTING.md.
问题类别 · Category

UI / 界面体验 · UI / UX

涉及的 Agent 框架 · Agent framework

ZCode Agent(自研)

严重程度 · Severity

阻塞使用 · Blocking (无法使用核心功能 / core function unusable)

复现频率 · Reproducibility

必现 · Always

问题描述 · Description

Problem: ZCode desktop 3.1.4 stays stuck on "Connecting" when using Z.ai models directly (api.z.ai).

  • GET /api/monitor/usage/quota/limit fails repeatedly (11–22824 ms timeouts)
  • POST /api/anthropic/v1/messages returns HTTP 529 (overloaded_error) intermittently
  • Same models work fine when routed through local NVIDIA NIM proxy (127.0.0.1:8082)

Impact: Daily occurrence (189 failures on 2026-06-22, 76 on 2026-06-23). ZCode unusable with Z.ai without third-party proxy.

Evidence: Logs attached — entitlement check is the primary blocker. Direct curl from same machine succeeds (200/0.83s), so server is reachable.

Requested fixes:

  • Z.ai: stabilize /api/monitor/usage/quota/limit, add Retry-After header for 529
  • ZCode: don't block session startup on entitlement failure, add retry with exponential backoff, show actionable error instead of infinite spinner

Full details below ↓

zai-connecting-issue.md

复现步骤 · Steps to reproduce

up

期望表现 · Expected behavior

up

实际表现 · Actual behavior

up

ZCode 版本 · ZCode version

3.1.4

设备 / 系统 / 浏览器 · Device / OS / Browser
截图 / 录屏 / 日志 · Screenshots / Recordings / Logs

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the attached zai-connecting-issue.md and its logs, then verify the reported quota and messages endpoints against the ZCode 3.1.4 and local NVIDIA NIM proxy details. The issue spans Z.ai and ZCode, so confirm which project owns each requested change; done requires an agreed scope and a reproducible resolution for the persistent Connecting state.

Written by the indexing model from the issue text.

Assessment

Domain
api, backend-api-design, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.