Cairn
NousResearch/hermes-agent

ZAI provider base_url config ignored; endpoint routing issues

Cluster 18302 · agent. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
7items grouped
Known?
Yes. 7 related items grouped here, 3 issues already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 1 PR.

Most members report that the ZAI/GLM provider does not honor a configured base_url, with related pull requests proposing changes to respect it or route manual-pool entries through a resolver. One member is adjacent: it concerns hermes auth add stamping a default base_url for the kimi-coding provider, not ZAI.

Open issues1

  • Issue#18302[Bug]: ZAI/GLM provider base_url causes 429/404 errors — config ignored by 5 code paths

Open PRs1

  • PR#37816Respect configured ZAI base URL

2 PRs closed without merging

From the close comments: superseded by another PR 2

  • #58088 fix(zai): honor configured base url · superseded by another PR → 23d3eda
  • #61575 fix(agent): route Z.AI manual-pool entries through _resolve_zai_base_url · superseded by another PR
Closed issues · 3
  • Closed#58071[Bug] zai provider ignores config.yaml base_url and always probes endpoints in hardcoded order — standard endpoint always wins over coding endpoint
  • Closed#61563zai manual-pool credentials always routed to metered /api/paas/v4 instead of /api/coding/paas/v4 (hermes auth add cannot override base_url)
  • Closed#68239hermes auth add stamps registry-default base_url for kimi-coding — sk-kimi- keys paired with api.moonshot.ai/v1, instant 401
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.19: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
agent
Closed issues
3
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/18302.json
cluster/18302.md