Cairn
NousResearch/hermes-agent

Dashboard auth: reverse proxies, PKCE cookies, native callbacks

Cluster 94733 · dashboard. Data as of

1 open item. Fix merged in #99176 on 31 Aug 2026. Check it covers your case.

The short answer

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

The members all concern dashboard authentication, covering trust of configured reverse proxies, URL-encoding the PKCE cookie value for strict proxy hops, and allowing configured native app callbacks (including private-use schemes for iOS). They share a broad area but span a few adjacent themes rather than one single problem.

Open issues1

  • Issue#94733Dashboard native auth: allow configured private-use callbacks for iOS

Open PRs0

No open pull requests.

Fixes on record

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

  • #94126 fix(dashboard): trust configured reverse proxies

    merged to main

    files: cli-config.yaml.example, hermes_cli/config_defaults.py, hermes_cli/web_server.py, pyproject.toml, tests/hermes_cli/test_dashboard_auth_gate.py, website/docs/user-guide/configuration.md, website/docs/user-guide/docker.md, website/docs/user-guide/features/web-dashboard.md

  • #99176 fix(dashboard-auth): url-encode the PKCE cookie value so strict proxy hops stop dropping it

    merged to main

    files: hermes_cli/dashboard_auth/cookies.py, hermes_cli/dashboard_auth/routes.py, tests/hermes_cli/test_dashboard_auth_cookies.py, tests/hermes_cli/test_dashboard_auth_native_flow.py

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #94771 dashboard auth: allow exact configured native app callbacks · superseded by another PR → 1f99a4b, #99176, #94126
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
#94126, #99176
Closed issues
0
Attempts
1 PR closed without merging
Fix link checked
31 Aug 2026

For your agent

The same facts, typed.

cluster/94733.json
cluster/94733.md