fix(dashboard): chat tab works in gated (OAuth) mode - #34793
Merged
Conversation
The Chat/TUI dashboard tab showed a false "Session token unavailable" error and never rendered the terminal whenever the dashboard ran in gated mode (OAuth auth gate active, --insecure not set), even though the user was fully authenticated and every other tab worked. Two checks in ChatPage.tsx gated purely on window.__HERMES_SESSION_TOKEN__, which the server intentionally omits in gated mode (web_server.py only injects __HERMES_AUTH_REQUIRED__=true there; the SPA is expected to use cookie auth + a single-use WS ticket). buildWsAuthParam() already resolves WS auth correctly for both modes, but the early bail prevented the effect from ever reaching it. Both checks now also honor __HERMES_AUTH_REQUIRED__: the banner no longer fires and the xterm/WS effect no longer bails in gated mode. Reported-by: wbrione <wbrione@users.noreply.github.com> Closes #34755
Contributor
🔎 Lint report:
|
alt-glitch
added
type/bug
KKT-OPT
pushed a commit
to KKT-OPT/hermes-agent
that referenced
this pull request
May 31, 2026
) The Chat/TUI dashboard tab showed a false "Session token unavailable" error and never rendered the terminal whenever the dashboard ran in gated mode (OAuth auth gate active, --insecure not set), even though the user was fully authenticated and every other tab worked. Two checks in ChatPage.tsx gated purely on window.__HERMES_SESSION_TOKEN__, which the server intentionally omits in gated mode (web_server.py only injects __HERMES_AUTH_REQUIRED__=true there; the SPA is expected to use cookie auth + a single-use WS ticket). buildWsAuthParam() already resolves WS auth correctly for both modes, but the early bail prevented the effect from ever reaching it. Both checks now also honor __HERMES_AUTH_REQUIRED__: the banner no longer fires and the xterm/WS effect no longer bails in gated mode. Reported-by: wbrione <wbrione@users.noreply.github.com> Closes NousResearch#34755
1 task
alt-glitch
pushed a commit
that referenced
this pull request
Jun 14, 2026
The Chat/TUI dashboard tab showed a false "Session token unavailable" error and never rendered the terminal whenever the dashboard ran in gated mode (OAuth auth gate active, --insecure not set), even though the user was fully authenticated and every other tab worked. Two checks in ChatPage.tsx gated purely on window.__HERMES_SESSION_TOKEN__, which the server intentionally omits in gated mode (web_server.py only injects __HERMES_AUTH_REQUIRED__=true there; the SPA is expected to use cookie auth + a single-use WS ticket). buildWsAuthParam() already resolves WS auth correctly for both modes, but the early bail prevented the effect from ever reaching it. Both checks now also honor __HERMES_AUTH_REQUIRED__: the banner no longer fires and the xterm/WS effect no longer bails in gated mode. Reported-by: wbrione <wbrione@users.noreply.github.com> Closes #34755
T02200059
pushed a commit
to T02200059/hermes-agent
that referenced
this pull request
Jun 18, 2026
) The Chat/TUI dashboard tab showed a false "Session token unavailable" error and never rendered the terminal whenever the dashboard ran in gated mode (OAuth auth gate active, --insecure not set), even though the user was fully authenticated and every other tab worked. Two checks in ChatPage.tsx gated purely on window.__HERMES_SESSION_TOKEN__, which the server intentionally omits in gated mode (web_server.py only injects __HERMES_AUTH_REQUIRED__=true there; the SPA is expected to use cookie auth + a single-use WS ticket). buildWsAuthParam() already resolves WS auth correctly for both modes, but the early bail prevented the effect from ever reaching it. Both checks now also honor __HERMES_AUTH_REQUIRED__: the banner no longer fires and the xterm/WS effect no longer bails in gated mode. Reported-by: wbrione <wbrione@users.noreply.github.com> Closes NousResearch#34755
waefrebeorn
pushed a commit
to waefrebeorn/slermes
that referenced
this pull request
Jul 2, 2026
) The Chat/TUI dashboard tab showed a false "Session token unavailable" error and never rendered the terminal whenever the dashboard ran in gated mode (OAuth auth gate active, --insecure not set), even though the user was fully authenticated and every other tab worked. Two checks in ChatPage.tsx gated purely on window.__HERMES_SESSION_TOKEN__, which the server intentionally omits in gated mode (web_server.py only injects __HERMES_AUTH_REQUIRED__=true there; the SPA is expected to use cookie auth + a single-use WS ticket). buildWsAuthParam() already resolves WS auth correctly for both modes, but the early bail prevented the effect from ever reaching it. Both checks now also honor __HERMES_AUTH_REQUIRED__: the banner no longer fires and the xterm/WS effect no longer bails in gated mode. Reported-by: wbrione <wbrione@users.noreply.github.com> Closes NousResearch#34755
santhreal
pushed a commit
to santhreal/hermes-agent
that referenced
this pull request
Jul 13, 2026
) The Chat/TUI dashboard tab showed a false "Session token unavailable" error and never rendered the terminal whenever the dashboard ran in gated mode (OAuth auth gate active, --insecure not set), even though the user was fully authenticated and every other tab worked. Two checks in ChatPage.tsx gated purely on window.__HERMES_SESSION_TOKEN__, which the server intentionally omits in gated mode (web_server.py only injects __HERMES_AUTH_REQUIRED__=true there; the SPA is expected to use cookie auth + a single-use WS ticket). buildWsAuthParam() already resolves WS auth correctly for both modes, but the early bail prevented the effect from ever reaching it. Both checks now also honor __HERMES_AUTH_REQUIRED__: the banner no longer fires and the xterm/WS effect no longer bails in gated mode. Reported-by: wbrione <wbrione@users.noreply.github.com> Closes NousResearch#34755
donbowman
pushed a commit
to donbowman/hermes-agent
that referenced
this pull request
Jul 13, 2026
) The Chat/TUI dashboard tab showed a false "Session token unavailable" error and never rendered the terminal whenever the dashboard ran in gated mode (OAuth auth gate active, --insecure not set), even though the user was fully authenticated and every other tab worked. Two checks in ChatPage.tsx gated purely on window.__HERMES_SESSION_TOKEN__, which the server intentionally omits in gated mode (web_server.py only injects __HERMES_AUTH_REQUIRED__=true there; the SPA is expected to use cookie auth + a single-use WS ticket). buildWsAuthParam() already resolves WS auth correctly for both modes, but the early bail prevented the effect from ever reaching it. Both checks now also honor __HERMES_AUTH_REQUIRED__: the banner no longer fires and the xterm/WS effect no longer bails in gated mode. Reported-by: wbrione <wbrione@users.noreply.github.com> Closes NousResearch#34755
Gravezzz
pushed a commit
to Gravezzz/hermes-agent
that referenced
this pull request
Jul 21, 2026
) The Chat/TUI dashboard tab showed a false "Session token unavailable" error and never rendered the terminal whenever the dashboard ran in gated mode (OAuth auth gate active, --insecure not set), even though the user was fully authenticated and every other tab worked. Two checks in ChatPage.tsx gated purely on window.__HERMES_SESSION_TOKEN__, which the server intentionally omits in gated mode (web_server.py only injects __HERMES_AUTH_REQUIRED__=true there; the SPA is expected to use cookie auth + a single-use WS ticket). buildWsAuthParam() already resolves WS auth correctly for both modes, but the early bail prevented the effect from ever reaching it. Both checks now also honor __HERMES_AUTH_REQUIRED__: the banner no longer fires and the xterm/WS effect no longer bails in gated mode. Reported-by: wbrione <wbrione@users.noreply.github.com> Closes NousResearch#34755
leewenjie
pushed a commit
to leewenjie/hermes-agent
that referenced
this pull request
Aug 7, 2026
) The Chat/TUI dashboard tab showed a false "Session token unavailable" error and never rendered the terminal whenever the dashboard ran in gated mode (OAuth auth gate active, --insecure not set), even though the user was fully authenticated and every other tab worked. Two checks in ChatPage.tsx gated purely on window.__HERMES_SESSION_TOKEN__, which the server intentionally omits in gated mode (web_server.py only injects __HERMES_AUTH_REQUIRED__=true there; the SPA is expected to use cookie auth + a single-use WS ticket). buildWsAuthParam() already resolves WS auth correctly for both modes, but the early bail prevented the effect from ever reaching it. Both checks now also honor __HERMES_AUTH_REQUIRED__: the banner no longer fires and the xterm/WS effect no longer bails in gated mode. Reported-by: wbrione <wbrione@users.noreply.github.com> Closes NousResearch#34755
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The dashboard Chat/TUI tab now renders correctly in gated (OAuth) mode instead of showing a false "Session token unavailable" error.
Root cause: two checks in
ChatPage.tsxgated purely onwindow.__HERMES_SESSION_TOKEN__, which the server intentionally omits in gated mode (web_server.pyinjects only__HERMES_AUTH_REQUIRED__=truethere; the SPA is expected to use cookie auth + a single-use WS ticket).buildWsAuthParam()inapi.tsalready resolves WS auth correctly for both modes, but the early bail prevented the effect from ever reaching it.Changes
web/src/pages/ChatPage.tsx:buildWsAuthParam().__HERMES_AUTH_REQUIRED__?: booleanto the localWindowglobal decl (already declared inapi.ts/gatewayClient.ts).Validation
--insecuremodewebhas no JS unit suite — verified vianpm run build(tsc -b type-check + vite build): passes clean.Reported and fix verified by @wbrione on a self-hosted OIDC deployment. Closes #34755.
Infographic