hermes - 💡(How to fix) Fix [Bug]: Infinite reload loop / React state loop on Sessions tab (Firefox + Chrome) — repeated 401 on /api/auth/me (v0.15.0) [1 pull requests]

Bug Description

General description:

Firefox:

1. The dashboard frontend (in index-DIruiv2Z.js) calls getAuthMe() → GET /api/auth/me It gets back 401 Unauthorized every single time.

2. The error-handling code treats this as a “stale token / auth failure” and immediately retries (or triggers a full page reload in Firefox).

3. That retry causes another render → another getAuthMe() → infinite loop.

Firefox: The recovery path does a full Navigated to /sessions instead → the reload storm you saw first.

Chrome:

1. Repeated stack trace (wx, qn, unstable_scheduleCallback, postMessage etc.) — it’s a React re-render / polling loop.

Same issue likely: #34202

Loosely Related:

Plugin 404 for /dashboard-plugins/example/dist/index.js (and sometimes kanban/hermes-achievements) → this is a known bug (GitHub issue #28609). The dashboard discovers the example plugin but its built dist/ folder is missing, so it spams errors on every load.

Steps to Reproduce

1. Ensure the gateway is running.
2. http://127.0.0.1:9119/sessions

You should see the behavior, if not, CTRL-R should show the behavior.

Expected Behavior

Expected behavior is not to have it reload endlessly.

Actual Behavior

The browser loops over and over until stopped / navigated away from.

Affected Component

Other

Messaging Platform (if gateway-related)

No response

Debug Report

Report:  https://paste.rs/WYHja
agent.log: https://paste.rs/VmL4t
gateway.log: https://paste.rs/3CSSu

Operating System

Ubuntu 24.04.4 LTS (WSL)

Python Version

Python: 3.11.15

Hermes Version

Hermes Agent v0.15.0 (2026.5.28)

Additional Logs / Traceback (optional)

NOTES:

The root trigger is a repeated 401 Unauthorized on /api/auth/me.
- In Chrome → causes React render loop (getAuthMe → unstable_scheduleCallback spam)
- In Firefox → causes full page reload storm ("Navigated to /sessions")
This happens on a fresh Incognito window and on normal window. Does NOT happen in Chrome with the same steps (UI stays usable, just console spam).

Plugin 404 for /dashboard-plugins/example/dist/index.js is already tracked in #28609.
This hermes dashboard instance is on port 9120, that is expected and configured deliberately by the user.
 
Firefox browser logs:
Navigated to http://127.0.0.1:9120/sessions
XHRGET http://127.0.0.1:9120/api/auth/me [HTTP/1.1 401 Unauthorized ...]
Navigated to http://127.0.0.1:9120/sessions
XHRGET http://127.0.0.1:9120/api/auth/me [HTTP/1.1 401 Unauthorized ...]
Navigated to http://127.0.0.1:9120/sessions
... (repeats over and over)

Chrome logs:
GET http://127.0.0.1:9120/api/auth/me 401 (Unauthorized)
Re @ index-DIruiv2Z.js:11
getAuthMe @ index-DIruiv2Z.js:11
(anonymous) @ index-DIruiv2Z.js:11
uc @ index-DIruiv2Z.js:8
wx @ index-DIruiv2Z.js:8
qn @ index-DIruiv2Z.js:8
wx @ index-DIruiv2Z.js:8
qn @ index-DIruiv2Z.js:8
... (repeats many times with unstable_scheduleCallback, postMessage, etc.)

Root Cause Analysis (optional)

No response

Proposed Fix (optional)

No response

Are you willing to submit a PR for this?

• I'd like to fix this myself and submit a PR