NousResearch/hermes-agent

Gateway auth 401 vs provider key error distinction

Cluster 39365 · apps/desktop. Data as of

Nothing open on GitHub. Fix merged in #70169 on 23 Jul 2026. Check it covers your case.

The short answer

0open issues
0open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #70169. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #70169. That is separate from the fix event.
Still open
Nothing open on GitHub.

These items concern a bug where a gateway authentication failure (401 on API_SERVER_KEY) was misreported as a missing OpenRouter API key, along with related fixes to distinguish gateway auth errors from provider key errors and improve failure notification handling in the desktop client.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #70169 fix(gateway): distinguish gateway auth 401 from provider API key errors (#39439 salvage, fixes #39365)

    merged to main

    files: agent/error_classifier.py, apps/desktop/src/i18n/en.ts, apps/desktop/src/i18n/ja.ts, apps/desktop/src/i18n/types.ts, apps/desktop/src/i18n/zh-hant.ts, apps/desktop/src/i18n/zh.ts, apps/desktop/src/store/notifications.test.ts, apps/desktop/src/store/notifications.ts, gateway/platforms/api_server.py, tests/gateway/test_session_api.py

2 PRs closed without merging

From the close comments: merged via another change 1 · superseded by another PR 1

  • #39439 fix(gateway): distinguish gateway auth 401 from provider API key errors · merged via another change → #70169, #39365
  • #65411 fix(desktop): add retry action to branch-failure notification · superseded by another PR → #128547
Closed issues · 1
  • Closed#39365[Bug]: Hermes Desktop shows misleading "OpenRouter API key missing" when the real failure is a 401 invalid API_SERVER_KEY (gateway auth)
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.50: 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
apps/desktop
Merged PRs
#70169
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
23 Jul 2026

For your agent

The same facts, typed.