📝 docs: generation-debug covers off-screen RAG, search, and persist skip
📝 docs: builtin tools and Knowledge Base also continue after you leave a topic With the tab open, KB retrieval and built-in tools keep going in the background; you do not need to switch back.
📝 docs: model continues immediately after MCP when you leave a topic With the tab still open, the summary starts after the tool returns; resume on return is only a backup.
📝 docs: log when MCP tools finish but the model never summarizes CHATHUB_GENERATION_DEBUG now records tool_loop_continue and skip reasons for the leave/return stall after a successful Tavily (or other MCP) call.
📝 docs: browser-fallback tools now continue the model after you leave
📝 docs: note leave/return generation-debug events for background topics
📝 docs: note spinning topic icon while a turn is still generating
📝 docs: document deferred browser Leave vs Stop and tool resume
📝 docs: document send-path enqueue_rejected and execute_retrying Browser fallbacks after a durable send request now leave a matching enqueue_rejected; empty-title retries appear as execute_retrying. Co-authored-by: Cursor <cursoragent@cursor.com>
📝 docs: Artifacts run on the durable background worker Prompt-only Artifacts stay on Graphile; DALL·E, code interpreter, and non-HTTP MCP still force the connected tab. Co-authored-by: Cursor <cursoragent@cursor.com>
📝 docs: document worker, delivery, and event-drop generation debug events
📝 docs: document CHATHUB_GENERATION_DEBUG send-path diagnostics New operator section for the durable generation send-path switch: values, client event gating via server config and localStorage override, event table, span correlation, privacy guarantees, and an Axiom query. Also adds the component-table and quick-reference rows.
📝 docs: browser-fallback replies are saved even after switching topics
📝 docs: document guaranteed background topic title retry A title job that starts before message binding lands now retries with backoff until the transcript is available; the chat reply is never affected by a title failure.
📝 docs: document leave/return vs Stop for background generation Topic switch, mobile back, and PWA close are not Stop; kagi/artifacts force the connected tab and show expected UNPROCESSABLE_CONTENT.
📝 docs: document background-generation debug env wiring Worker chat now uses the same CHATHUB_TOOLS_DEBUG, DEBUG_*_CACHE, and CHATHUB_KNOWLEDGE_DEBUG switches as HTTP routes in the same process.
📝 docs: document graphile-worker tslib image boot failure Operators looping on Failed to prepare server / Cannot find module tslib need to upgrade the image; disabling the worker does not skip that import.
📝 docs: document per-row leftover cleanup savepoints Clarify that a leftover that cannot be cleaned is skipped so later jobs in the same recovery pass still finish.
📝 docs: document leftover cleanup isolation after a failed job
📝 docs: document atomic child-id append and unmarked terminal drain
📝 docs: document dangling-assistant recovery and terminal placeholder sweep
📝 docs: document supervisor placeholder cleanup on cancel and sweep
📝 docs: document request-scoped durable jobs and placeholder cleanup
📝 docs: distinguish standalone threads and group lanes Document per-agent group lanes, follow-up supervisor rounds, and standalone versus continuation thread history.
📝 docs: add background conversation generation hub and cross-links Document default-on server replies, browser fallback, worker env, and how related features interact after a tab close.
docs(image): restored conversations require explicit Retry for chat images
📝 docs: write-first task durability wording (round-10)
📝 docs: accurate package availability + implemented task-recovery guarantee (round-9 R9-6)
📝 docs: background chat image generation + bundled Python packages
📝 docs: best-effort telemetry caveats — absent reports/events are inconclusive (round-7 R7-2)