Teknium 3c73d1852e docs: remote desktop connect needs --tui on the backend (#38350) ... The Desktop App and Web Dashboard remote-connect instructions told users to start the backend with `hermes dashboard --no-open --insecure --host 0.0.0.0`, omitting --tui. Without --tui the embedded-chat WebSockets (/api/ws, /api/pty) are refused, so the desktop passes the /api/status health check and reports the backend "ready" — but chat never works because the socket is closed on connect. - Add --tui to both backend command blocks (with an inline why-comment). - Explain that the desktop chat runs over /api/ws + /api/pty and needs the embedded-chat surface enabled; a plain dashboard/gateway is not enough. - Add a troubleshooting entry for the exact symptom (connects, says ready, chat dead) on both pages.		2026-06-03 09:30:20 -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(xai): route video models by modality	2026-06-01 19:00:30 -07:00
integrations	docs: drop early-beta framing for native Windows support (#36093)	2026-05-31 15:33:18 -07:00
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: remote desktop connect needs --tui on the backend (#38350)	2026-06-03 09:30:20 -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