Cairn
NousResearch/hermes-agent

Dashboard gated/basic_auth mode: session token and OAuth/reveal issues

Cluster 55210 · dashboard. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
7items grouped
Known?
Yes. 7 related items grouped here, 3 issues already closed.
Fix event
No fix has been merged to main. 4 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

Members describe problems in the dashboard's gated (basic_auth) mode, where a legacy session token placeholder is reportedly not injected, affecting model-provider OAuth login and the Keys page reveal button. Several pull requests propose related changes such as injecting a token or using cookie/fetchJSON auth, but the members do not confirm outcomes.

Open issues0

No open issues.

Open PRs0

No open pull requests.

4 PRs closed without merging

From the close comments: done elsewhere 2 · superseded by another PR 1 · other 1

  • #55220 fix(dashboard): use fetchJSON auth in revealEnvVar for gated mode · superseded by another PR → #51156
  • #55221 fix(dashboard): inject placeholder session token in gated mode so reveal works · done elsewhere → 3e24b16, #51156, #55220
  • #58211 fix(dashboard): allow provider oauth with cookie auth · other → 3e24b16
  • #59663 fix(dashboard): inject session token in gated index.html so model-provider OAuth works under basic_auth (#59274) · done elsewhere → 3e24b16, #59274
Closed issues · 3
  • Closed#55210Bug: Dashboard Keys page reveal button throws in gated (basic_auth) mode — frontend never sends the request
  • Closed#58207[Bug]: Dashboard OAuth provider login fails in gated mode because startOAuthLogin requires legacy session token
  • Closed#59274Dashboard model-provider OAuth fails under basic_auth: `__HERMES_SESSION_TOKEN__` never injected ("Session token not available")
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.24: 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
Closed issues
3
Attempts
4 PRs closed without merging

For your agent

The same facts, typed.

cluster/55210.json
cluster/55210.md