NousResearch/hermes-agent

Z.AI provider error detection and pool rotation fixes

Cluster 61487. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue 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
Nothing open on GitHub.

These items address bugs and refactors in how Z.AI provider errors are classified (payment, server, unavailable) and how credential pool rotation behaves when quota or usage limits are reached. A related bug reports incorrect cascade-marking of all pool keys when one key hits its quota.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: superseded by another PR 2

  • #61492 fix(auxiliary): exclude Z.AI Coding Plan rolling quotas from payment error detection · superseded by another PR → #62467
  • #61575 fix(agent): route Z.AI manual-pool entries through _resolve_zai_base_url · superseded by another PR
Closed issues · 1
  • Closed#61487[Bug]: zai provider pool cascade-marks every key when one hits per-key quota 1308/1113
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.67: 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

Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.