Dashboard /api/auth/me 401 loop in loopback mode
NousResearch/hermes-agent · cluster 34202 · dashboard
Data as of
Nothing open on GitHub. Fix merged in #133983. Check it covers your case.
The short answer
- Known?
- Yes. 8 related items grouped here, 5 issues already closed.
- Fix event
- A fix was merged to main in PR #133983. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
partially resolved, deciding PRs #34222, #133983. That is separate from the fix event. - Still open
- Nothing open on GitHub.
Multiple bug reports, fixes, and a release centered on the dashboard entering an infinite reload loop when /api/auth/me returns 401 in loopback or no-OAuth configurations. Related pull requests address token handling and endpoint authentication behavior in that mode.
Open issues0
Open PRs0
Fixes on record
-
#133983 fix(dashboard): report the loopback identity from /api/auth/me instead of 401
files:
hermes_cli/dashboard_auth/routes.py,tests/hermes_cli/test_dashboard_auth_middleware.py,web/src/components/AuthWidget.test.tsx,web/src/components/AuthWidget.tsx,web/src/components/auth-widget-visibility.ts,web/src/lib/api.test.ts,web/src/lib/api.ts -
#34222 chore: release v0.15.1 (2026.5.29)
files:
RELEASE_v0.15.1.md,acp_registry/agent.json,hermes_cli/__init__.py,pyproject.toml
1 PR closed without merging
From the close comments: superseded by another PR 1
- #66295 fix(dashboard): return loopback identity from /api/auth/me with valid token (#66223) · superseded by another PR
Closed issues · 5
- Closed#34202Dashboard infinite reload loop in loopback mode — GET /api/auth/me returns 401 on every page load
- Closed#34206[Bug]: Infinite reload loop / React state loop on Sessions tab (Firefox + Chrome) — repeated 401 on /api/auth/me (v0.15.0)
- Closed#34289v0.15.0: dashboard SPA reload-loops in loopback mode — /api/auth/me always 401s when auth gate is off
- Closed#34398Dashboard SPA reload loop on /api/auth/me when running with --insecure (no OAuth provider)
- Closed#66223Dashboard loopback: /api/auth/me 401 with valid token causing blank screen
How this cluster was grouped
-
Link evidence (
partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text. - Members outside that structural core may belong to a different underlying problem.
-
Pairwise link density
0.27: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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