Dashboard session token scraping fails when dashboard responds with HTTP 302 (no HTML body)

[ismaelmmachado]

Comportamento observado

Mesmo com o gateway saudável (/health: ok) e chat respondendo, a UI do Workspace exibe:

• Authentication required
• Hermes Agent rejected the connection token.
• Go to Settings -> Advanced -> Hermes Agent to update your token.

Na prática, o backend lança Dashboard session token not found in root HTML porque o dashboard retorna HTTP 302 com corpo vazio na raiz /, sem injetar o token esperado pelo regex.

Ambiente

• hermes-agent: v0.17.0
• Workspace: vite dev (hermes-workspace)
• Dashboard com basic_auth
• OS: Linux container
• Portas: gateway 8642, dashboard 9119, workspace 3000

Caminho afetado

src/server/gateway-capabilities.ts:279 (fetchDashboardToken()) faz fetch em CLAUDE_DASHBOARD_URL + "/" e aplica regex em HTML vazio/302.

[tilottamwagh]

Hi Team, When this issue will resolved ?

[emaxgms]

This is happening to me, i have everything configured correctly, dashboard showing, api enabled, all good.
But hermes-workspace cant load any information about my Hermes Agent, nor sessions, models, skills, files, anything its just empty.
Can this be about the new 0.17 update that enforce Authentication with username and password for dashboard ?