1 commit

Author	SHA1	Message	Date
Brooklyn Nicholson	25ba6783b8	feat(tui-gateway): WebSocket transport + /chat web UI, wire-compatible with Ink ... Extracts the JSON-RPC transport from stdio into an abstraction so the same dispatcher drives Ink over stdio AND browser/iOS clients over WebSocket without duplicating handler logic. Adds a Chat page to the existing web dashboard that exercises the full surface — streaming, tool calls, slash commands, model picker, session resume. Backend ------- * tui_gateway/transport.py — Transport protocol + contextvar binding + the module-level StdioTransport. Stream is resolved through a callback so tests that monkeypatch `_real_stdout` keep working. * tui_gateway/server.py — write_json and dispatch are now transport-aware. Backward compatible: no transport bound = legacy stdio path, so entry.py (Ink's stdio entrypoint) is unchanged externally. * tui_gateway/ws.py — WSTransport + handle_ws coroutine. Safe to call from any thread: detects loop-thread deadlock and fire-and-forget schedules when needed, blocking run_coroutine_threadsafe + future.result otherwise. * hermes_cli/web_server.py — mounts /api/ws on the existing FastAPI app, gated by the same ephemeral session token used for REST. Adds HERMES_DASHBOARD_DEV_TOKEN env override so Vite HMR dev can share the token with the backend. Frontend -------- * web/src/lib/gatewayClient.ts — browser WebSocket JSON-RPC client that mirrors ui-tui/src/gatewayClient.ts. * web/src/lib/slashExec.ts — slash command pipeline (slash.exec with command.dispatch fallback + exec/plugin/alias/skill/send directive handling), mirrors ui-tui/src/app/createSlashHandler.ts. * web/src/pages/ChatPage.tsx — transcript + composer driven entirely by the WS. * web/src/components/SlashPopover.tsx — autocomplete popover above the composer, debounced complete.slash. * web/src/components/ModelPickerDialog.tsx — two-stage provider/model picker; confirms by emitting /model through the slash pipeline. * web/src/components/ToolCall.tsx — expandable tool call row (Ink-style chevron + context + summary/error/diff). * web/src/App.tsx — logo links to /, Chat entry added to nav. * web/src/pages/SessionsPage.tsx — every session row gets an Open-in-chat button that navigates to /chat?resume=<id> (uses session.resume). * web/vite.config.ts — /api proxy configured with ws: true so WebSocket upgrades forward in dev mode; injectDevToken plugin reads HERMES_DASHBOARD_DEV_TOKEN and injects it into the served index.html so Vite HMR can authenticate against FastAPI without a separate flow. Tests ----- tests/hermes_cli/test_web_server.py picks up three new classes: * TestTuiGatewayWebSocket — handshake, auth rejection, parse errors, unknown methods, inline + pool handler round-trips, session event routing, disconnect cleanup. * TestTuiGatewayTransportParity — byte-identical envelopes for the same RPC over stdio vs WS (unknown method, inline handler, error envelope, explicit stdio transport). * TestTuiGatewayE2EAnyPort — scripted multi-RPC conversation driven identically via handle_request and via WebSocket; order + shape must match. This is the "hermes --tui in any port" check. Existing tests under tests/tui_gateway/ and tests/test_tui_gateway_server.py all still pass unchanged — backward compat preserved. Try it ------ hermes dashboard # builds web, serves on :9119, click Chat Dev with HMR: export HERMES_DASHBOARD_DEV_TOKEN="dev-\$(openssl rand -hex 16)" hermes dashboard --no-open cd web && npm run dev # :5173, /api + /api/ws proxied to :9119 fix(chat): insert tool rows before the streaming assistant message Transcript used to read "user → empty assistant bubble → tool → bubble filling in", which is disorienting: the streaming cursor sits at the top while the "work" rows appear below it chronologically. Now tool.start inserts the row just before the current streaming assistant message, so the order reads "user → tools → final message". If no streaming assistant exists yet (rare), tools still append at the end; tool.progress / tool.complete match by id regardless of position. fix(web-chat): font, composer, streaming caret + port GoodVibesHeart - ChatPage root opts out of App's `font-mondwest uppercase` (dashboard chrome style) — adds `font-courier normal-case` so transcript prose is readable mono mixed-case instead of pixel-display caps. - Composer: textarea + send button wrapped as one bordered unit with `focus-within` ring; `font-sans` dropped (it mapped to `Collapse` display). Heights stretch together via `items-stretch`; button is a flush cap with `border-l` divider. - Streaming caret no longer wraps to a new line when the assistant renders a block element. Markdown now takes a `streaming` prop and injects the caret inside the last block (paragraph, list item, code) so it hugs the trailing character. Caret sized in em units. - EmptyState gets a blinking caret + <kbd> shortcut chips. - Port ui-tui's GoodVibesHeart easter egg to the web: typing "thanks" / "ty" / "ily" / "good bot" flashes a Lucide heart next to the connection badge (same regex, same 650ms beat, same palette as ui-tui/src/app/useMainApp.ts).	2026-04-23 21:11:04 -04:00