The Hermes Agent Dashboard keeps refreshing. The first step is not to clear the browser cache, but to confirm that you have installed v0.15.0. Nous Research released Hermes Agent v0.15.1 on May 29, 2026, specifically fixes the infinite refresh issue in Dashboard 401 in v0.15.0, especially affecting users of Docker, hosted Hermes, and newly installed loopback mode.
Why does it keep refreshing?
At the heart of this issue is the identity detection interface /api/auth/me. In loopback mode, returning 401 is normal behavior, but v0.15.0 treats this 401 as a session token change, triggering a full-page refresh. After refreshing, other interfaces succeed again, the refresh protection is cleared, and the page enters a loop. Firefox may keep jumping /sessions, while Chrome looks more like a page repeatedly re-rendered.
Fastest processing steps
- Run the
hermes --versionfirst to confirm if it is v0.15.0. - Run
hermes updateor upgrade to v0.15.1 as you installed. - Restart the
hermes gatewayor Docker container, then reopen the Dashboard. - If it still refreshes, check again whether there is a reverse proxy, browser extension, or an old dashboard static file cache.
Don't delete ~/.hermes right away, as that will wipe out configurations, conversations, and some states, which is too costly. The phenomenon of infinite dashboard refresh is more like a version bug, not like the wrong account password, nor like the model provider configuration error.
When is it necessary to check the internet?
After upgrading to v0.15.1, if the Dashboard still won't open but the page doesn't refresh repeatedly, it directly fails to connect, is blank, or 502, then checks ports, Docker mappings, reverse proxies, and gateway logs. The order of judgment is simple: repeatedly refresh to check the version; If you can't connect at all, then check the internet; If you can open it but the function is incorrect, check the configuration.
