Hermes Dashboard Session Expired Fix: Update to 0.21.3 (2026)

Update Hermes Agent to version 0.21.3 and the random dashboard logouts stop: that patch carries the hermes dashboard session expired fix, and according to the official release notes NousResearch published on GitHub on 14 September 2026, remote dashboard sessions no longer expire when refresh requests arrive in bursts. The bug hit hardest on Desktop wake-ups and busy connections — you would open your laptop, the dashboard would fire several refresh requests at once, and one of them would replay a login token that had already been rotated. The server treated that replay as a bad credential and ended your session. If you have been typing your credentials back in three times a day since the 0.21.0 release landed at the end of August, this page covers what broke, what the patch changes, and how to confirm the fix has actually taken on your machine.

📺 Watch: NEW Hermes Agent Update is WILD!

🔥 Get the Agent OS as a free bonus: AI Profit Boardroom members get the full Agent OS zip, prompt libraries, daily tutorials and weekly live coaching calls. → Get inside · Want AI SEO help 1-on-1? Book a free SEO strategy session →

Hermes Dashboard Session Expired Fix: What Actually Changed

The fix is tracked in the 0.21.3 release notes as item 110061, and the wording matters: remote dashboard sessions no longer expire on refresh bursts because both refresh paths now coalesce concurrent requests carrying the same rotating refresh token. In plain terms, the dashboard authenticates you with a token that changes every time it is used. When several refresh requests left your machine at once — which is exactly what happens when a Desktop machine wakes from sleep — the first request rotated the token and the rest arrived carrying the old one. Before 0.21.3, the gateway read those stragglers as replays of a dead token and expired the whole session. Now the gateway recognises that a burst of requests carrying the same rotating refresh token belongs to one legitimate refresh, merges them, and answers them together.

The same release note includes a second, quieter improvement: token refresh now runs off the event loop, so a slow identity provider no longer freezes the api status endpoint. If your dashboard sometimes hung entirely while logging you out, that hang and the logout were two symptoms of the same overloaded refresh path, and both are addressed in this patch.

Why Your Hermes Dashboard Kept Logging You Out

The pattern of the bug explains why it felt so random. A Hermes web interface session on a stable desk connection might never trigger it, while a laptop that sleeps and wakes several times a day tripped it constantly, because every wake produced exactly the burst of simultaneous refreshes the old code mishandled. Mobile connections that drop and reconnect produced the same signature. The session had not genuinely timed out and your credentials were never wrong — the gateway simply saw its own rotation race and blamed you for it. That is also why clearing the browser cache, re-pairing the Desktop app or reinstalling never cured it: the race lived on the server-side refresh path, not in anything stored on your machine. The full 0.21.3 patch notes write-up covers the release as a whole; this page stays on the session bug because it is the one that cost people the most working time.

If you want your agents earning around the clock instead of logging you out — the update checklists, 1,000+ workflows and weekly live coaching calls are all inside — check out the AI Profit Boardroom → join the operators here. Want a personal AI SEO roadmap first? Book a free SEO strategy session and get it mapped out 1-on-1.

How to Get the Fix on Your Machine

Hermes Agent 0.21.3 shipped on 14 September 2026 as a rollup of roughly 338 pull requests merged since 0.21.2, and the release notes list two supported update paths: run the hermes update command, or re-run the official installer. Either route lands you on the tagged stable build rather than a moving development version, which is what you want on any machine that stays switched on. The Hermes Agent installation guide walks through the full flow, including the checks worth running before and after the new build applies.

Three things are worth knowing before you press the button:

• Update the machine that runs the gateway, not just the machine showing the dashboard. The fix lives in the gateway refresh paths, so patching a viewing device alone changes nothing.
• The patch is cumulative. If you skipped 0.21.1 and 0.21.2, moving straight to 0.21.3 picks up their session-store repairs as well — the official changelog on hermes-ai.net describes the 11 September release as a patch specifically repairing session-store reliability regressions exposed after 0.21.0.
• Expect one final logout. Updating restarts the gateway, which ends live sessions once. Signing in after the update should be the last time the dashboard asks unprompted.

If Sessions Still Expire After Updating

A dashboard that still expires sessions after the update usually means one of three things, and each has a quick check. First, confirm the version actually changed — a running process started before the update keeps serving the old code until it restarts. Second, look at the health of the session database. The same 0.21.3 release fixed long-lived processes leaking duplicate writer handles against state.db, the SQLite database that stores session state; the notes say the warning about multiple live SessionDB handles stops firing on a healthy topology once gateway and dashboard readers attach read-only. If that warning still appears for you, work through the state.db locked fix, because a struggling session store can end sessions for its own reasons. Third, rule out the surface you are using: the hermes dashboard command guide covers how the dashboard is launched and where its logs land, which tells you whether the expiry is coming from the gateway or from the page in front of you.

One prompt you should not mistake for the old bug: 0.21.3 also tightened MCP authentication, with OAuth refresh tokens now bound to their issuer and a daily MCP re-auth nudge added in Desktop, per the same release notes. If Desktop asks you once a day to re-authorise an MCP connection, that is the new nudge doing its job deliberately — a security prompt, not a session expiring underneath you. The difference is scope: the nudge names a specific MCP server and appears predictably; the bug threw you out of the whole dashboard at random moments.

What This Means for Remote Hermes Setups

The dashboard session fix matters most if Hermes is the machine you manage a business from rather than a toy you open occasionally. A remote Hermes workspace on a VPS, checked from a laptop and a phone, produces exactly the wake bursts and reconnects that triggered the old bug — so remote-first operators were the ones paying for it daily. With 0.21.3 applied, the practical ceiling changes: you can leave an always-on agent dashboard open across devices and trust that coming back to it means picking up where you left off, not authenticating again. NousResearch flagged in the release notes that fuller documentation of the 0.21.x additions ships with 0.22.0, so treat this patch as the stability floor for whatever lands next.

If you are building towards that kind of setup, two resources on this site pair well with the patch. The Agent OS guide covers the operating structure that turns a stable agent into a system that runs whole workflows, and the Goldie Bench write-up covers how the main agent brains compare in hands-on tests, which is useful when you decide what model sits behind the dashboard you just stabilised.

The Bottom Line on the Session Expiry Bug

The hermes dashboard session expired fix is the reason to stop tolerating the logouts today: the cause was a token rotation race on the gateway, the cure is the 0.21.3 build from 14 September 2026, and the update takes minutes with the hermes update command. Patch the gateway machine, sign in once more, and if anything still expires, check the version, the state.db warnings and the dashboard logs in that order. Every claim above traces to the official NousResearch release notes on GitHub and the hermes-ai.net changelog, so when 0.22.0 arrives with the fuller documentation, you will already be standing on the stable base it assumes.

If you want a Hermes stack that stays up, stays signed in and quietly compounds — daily tutorials, the full Agent OS zip and weekly live coaching are waiting — check out the AI Profit Boardroom → get inside now. Rather talk it through first? Book a free SEO strategy session and get a plan for ranking with AI before your competitors do.

Real wins from inside the AI Profit Boardroom

See all 3,000+ members →

← Back to all posts