Cairn
NousResearch/hermes-agent

Dashboard auth refresh-token handling and session expiry

Cluster 55712 · dashboard. Data as of

Nothing open on GitHub. Fix merged in #110061 on 13 Sep 2026. Check it covers your case.

The short answer

0open issues
0open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #110061. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #110061. That is separate from the fix event.
Still open
Nothing open on GitHub.

Most members concern remote dashboard sessions expiring, linked to concurrent or bursty refresh requests and rotating refresh-token reuse detection; some titles describe proposed changes to coalesce refreshes or run them off the event loop. One member separately concerns skipping a legacy token check in gated mode, which is related to dashboard auth but may be a distinct change.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #110061 Remote dashboard sessions no longer expire on refresh bursts; refresh runs off the event loop (#55712, salvage #71548 #55717)

    merged to main

    files: evals/dashboard_auth/refresh_singleflight_live_e2e.py, hermes_cli/dashboard_auth/middleware.py, hermes_cli/dashboard_auth/refresh_singleflight.py, hermes_cli/dashboard_auth/routes.py, tests/hermes_cli/test_refresh_singleflight.py

2 PRs closed without merging

From the close comments: done elsewhere 2

  • #35500 fix(dashboard): skip legacy token check in gated mode for _require_token endpoints · done elsewhere → 63a421d, #42578
  • #55717 fix(dashboard-auth): coalesce concurrent refresh requests to prevent RT reuse detection · done elsewhere → 5dea46d, #110061
Closed issues · 1
  • Closed#55712Remote dashboard session expires due to rotating refresh-token replay
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
Merged PRs
#110061
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
13 Sep 2026

For your agent

The same facts, typed.

cluster/55712.json
cluster/55712.md