Cairn
NousResearch/hermes-agent

Invalid tokens incorrectly returning 503 instead of 401

Cluster 97361 · dashboard. Data as of

2 open items. Fix attempted, not merged.

The short answer

0open issues
2open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
0 issues and 2 PRs.

A bug where unrecognized or foreign session tokens trigger a 503 provider-unreachable error rather than an appropriate 401/None response, preventing clients from recovering. Multiple fixes address returning None or 401 for unparseable tokens.

Open issues0

No open issues.

Open PRs2

  • PR#97415fix(dashboard-auth): unparseable foreign tokens are 401s, not 503s
  • PR#97426fix(auth): return None for unrecognized tokens instead of 503 ProviderError

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #97362 fix(dashboard-auth): treat an unrecognised token as None, not as an unreachable IDP · superseded by another PR → #92828, #1, #97361
Closed issues · 1
  • Closed#97361[Bug]: a foreign or stale session token is reported as an unreachable IDP (503), so clients can never recover
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
dashboard
Closed issues
1
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/97361.json
cluster/97361.md