feat: add durable chat storage and disconnect recovery

2026-08-27 20:16:33 +10:00
parent 934a718c90
commit 1c5167b6e6
9 changed files with 709 additions and 184 deletions
@@ -18,9 +18,18 @@ Native-like Hermes dashboard plugin for local Ollama model management and chat.
 - Streamed Ollama responses with a real Stop action that cancels the active request
 - Minimized-by-default expandable thinking/progress details with live stage, elapsed time, event, and character counters
 - Validation harness mode: choose one primary model and one or more independent validator models; validators review the primary draft and the primary model compiles one final answer
+- Server-owned chat jobs continue after the browser closes and persist final answers for later resume
+- SQLite is the default chat store for new users
+- Optional native PostgreSQL storage can be installed and linked explicitly from the plugin

 The chat supports two modes. With one selected model, it sends a normal direct request. With one primary model and at least one validator model selected, the plugin runs a validation harness: the primary creates a draft, validators independently review the request and draft in parallel, and the primary compiles one final user-facing answer from the draft and validation reports. Validator reports are returned as supporting evidence, while only the compiled primary response is persisted and displayed as the answer.

+## Chat storage and durability
+
+Chat jobs are persisted before model execution. The browser observes job status through `/chat/status/{request_id}` but does not own generation. Closing the browser no longer cancels a queued or running job, and the dashboard recovers queued/running jobs after restart. Each conversation records immutable message versions, job attempts, stage timing, model metrics, and append-only operational events.
+
+SQLite remains the default and requires no service installation. The Chat storage panel can detect native PostgreSQL, install it only after explicit confirmation, and link it as the active backend. PostgreSQL storage uses the local service environment and remains disabled until the user explicitly selects **Link PostgreSQL**.
+

 ## Performance metrics