Cairn
NousResearch/hermes-agent

API server key config and error messaging issues

Cluster 33207 · gateway. Data as of

1 open item. Fix attempted, not merged.

The short answer

1open issue
0open PRs
3items grouped
Known?
Yes. 3 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
1 issue and 0 PRs.

These items concern problems with API server key configuration—specifically reusing existing config values for session continuation rather than requiring a separate env variable, and improving error messages when authentication fails. A desktop app session/duplicate reply issue is also grouped here.

Open issues1

  • Issue#33207Session continuation should reuse platforms.api_server.key instead of requiring separate API_SERVER_KEY

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: stale or abandoned 1 · other 1

  • #33364 fix(api-server): name both API_SERVER_KEY env and platforms.api_server.key in 403 messages · stale or abandoned
  • #33532 fix(config): coerce bare-string home_channel + improve api_server.key messages (fixes #33141, fixes #33207) · other → 50c66b2, #33141, #33207
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

Subsystem
gateway
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/33207.json
cluster/33207.md