Summary

Adds a Chat tab to the dashboard. Proxies to the gateway's existing API server (/v1/chat/completions) — no new agent lifecycle code, no new dependencies.

Backend — 2 endpoints, 110 lines

POST /api/chat/send — SSE streaming proxy to localhost:8642/v1/chat/completions

• Forwards messages + optional X-Hermes-Session-Id for session continuity
• Passes API_SERVER_KEY to the API server when set
• Handles empty stream (agent internal errors): detects finish_reason without content, falls back to a non-streaming request to surface the actual error message
• Respects API_SERVER_PORT env var

GET /api/chat/status — health check, hits the API server's /health endpoint

Both are protected by the existing auth middleware (#9800).

Frontend — ChatPage.tsx, 212 lines

• SSE stream parsing (OpenAI-compatible choices[0].delta.content chunks)
• Markdown rendering via existing Markdown component
• Session continuity (stores session ID from first response, sends on subsequent messages)
• Auto-scroll to bottom on new content
• Auto-resize textarea, Enter to send, Shift+Enter for newline
• When gateway isn't running: "Chat unavailable" with hermes gateway start instruction
• i18n: English + Chinese translations

Requires

The gateway must be running with the api_server platform enabled:

# ~/.hermes/config.yaml
platforms:
  api_server:
    enabled: true

Then hermes gateway start. The Chat tab detects this automatically and shows setup instructions if not configured.

Files changed