Issue Station
Sign In
Tools hereToolbox

hermes - 💡(How to fix) Fix hermes status: Z.AI / GLM key not detected when using ZAI_API_KEY env var

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Root Cause

hermes_cli/status.py line 134 only checks GLM_API_KEY:

"Z.AI / GLM": "GLM_API_KEY",

But the vault bridge materializes Z.ai credentials as ZAI_API_KEY (and some users may use Z_AI_API_KEY). The status check should accept any of these alternate env var names, consistent with how other providers (e.g. Anthropic, Google / Gemini) handle multiple env var names.

Fix Action

Fix

Change to a tuple of alternates:

"Z.AI / GLM": ("GLM_API_KEY", "ZAI_API_KEY", "Z_AI_API_KEY"),

Code Example

"Z.AI / GLM": "GLM_API_KEY",

---

"Z.AI / GLM": ("GLM_API_KEY", "ZAI_API_KEY", "Z_AI_API_KEY"),

---

Z.AI / GLM    ✓ ab7d...10Lx
RAW_BUFFERClick to expand / collapse

Bug

hermes status shows Z.AI / GLM ✗ (not set) even when ZAI_API_KEY is present in ~/.hermes/.env (materialized from Hermes Vault).

Root Cause

hermes_cli/status.py line 134 only checks GLM_API_KEY:

"Z.AI / GLM": "GLM_API_KEY",

But the vault bridge materializes Z.ai credentials as ZAI_API_KEY (and some users may use Z_AI_API_KEY). The status check should accept any of these alternate env var names, consistent with how other providers (e.g. Anthropic, Google / Gemini) handle multiple env var names.

Fix

Change to a tuple of alternates:

"Z.AI / GLM": ("GLM_API_KEY", "ZAI_API_KEY", "Z_AI_API_KEY"),

Verification

After the fix, hermes status correctly shows:

Z.AI / GLM    ✓ ab7d...10Lx

Prompt to Recreate

  1. Set ZAI_API_KEY in ~/.hermes/.env (or let vault bridge materialize it)
  2. Run hermes status
  3. Observe Z.AI / GLM ✗ (not set) — should be ✓

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#tool integration#LLM response#prompt template#agent execution

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

hermes - 💡(How to fix) Fix hermes status: Z.AI / GLM key not detected when using ZAI_API_KEY env var