Z.AI/GLM API key detection in status command

NousResearch/hermes-agent · cluster 21990 · hermes cli

Data as of

4 open items. Fix attempted, not merged.

The short answer

2open issues
2open PRs
6items grouped
Known?
Yes. 6 related items grouped here, 0 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
2 issues and 2 PRs.

These issues and fixes address the status command failing to detect Z.AI/GLM credentials when stored under alternative environment variable names like ZAI_API_KEY or Z_AI_API_KEY. One member also adds broader first-class provider support for Z.AI/GLM, Kimi, and MiniMax.

Open issues2

  • Issue#21990hermes status: Z.AI / GLM key not detected when using ZAI_API_KEY env var
  • Issue#35266bug: status.py API Keys section only checks GLM_API_KEY for Z.AI / GLM, missing ZAI_API_KEY and Z_AI_API_KEY

Open PRs2

  • PR#23557fix(status): detect ZAI env vars in hermes status
  • PR#35274fix(status): check all Z.AI/GLM API key variants in status display

2 PRs closed without merging

From the close comments: stale or abandoned 2

  • #21991 fix(status): recognize ZAI API key aliases · stale or abandoned
  • #21993 fix(status): detect Z.AI / GLM key via ZAI_API_KEY env var · stale or abandoned
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.36: 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
hermes cli
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.