Teknium 63727f32bf docs(dashboard): document connecting Hermes Desktop to a remote backend (#38534) ... Desktop's readiness probe only checks GET /api/status (public), but the live chat rides /api/ws, which is gated by --tui (4403), a matching session token (4401), and a non-loopback bind. The web-dashboard doc covered --tui and the OAuth gate but never the Desktop remote-connection flow, so the three independent failure modes weren't documented together. Adds a 'Connecting Hermes Desktop to a remote backend' section: pin HERMES_DASHBOARD_SESSION_TOKEN, run with --host 0.0.0.0 --insecure --tui, the curl token-verification one-liner, and WS close-code triage.		2026-06-03 16:28:01 -07:00
..
developer-guide	fix(docs): remove remaining stale submodule references missed by #38089 (#38105)	2026-06-03 03:11:19 -07:00
getting-started	fix(windows): rip out unused submodule support in installer & docker & docs	2026-06-03 03:01:37 -07:00
guides	fix(cli): harden hermes portal SystemExit handling + finish model-pick doc sweep	2026-06-04 02:33:33 +05:30
integrations	fix(cli): harden hermes portal SystemExit handling + finish model-pick doc sweep	2026-06-04 02:33:33 +05:30
reference	feat(debug): include desktop.log in hermes debug share / /debug / hermes logs (#38203)	2026-06-03 05:41:35 -07:00
user-guide	docs(dashboard): document connecting Hermes Desktop to a remote backend (#38534)	2026-06-03 16:28:01 -07:00
index.mdx	Add Hermes desktop app (#20059)	2026-05-31 17:46:56 -05:00
user-stories.mdx	docs(website): add User Stories and Use Cases collage page (#18282)	2026-04-30 23:56:59 -07:00