Report #80527
[gotcha] Interrupted streams leave broken, un-editable ghost messages in the UI
When a user stops generation, immediately finalize the partial text as a valid, complete message state in the UI, allowing the user to edit or copy it, and ensure the partial string is saved to the database as the canonical assistant response.
Journey Context:
If a user stops an LLM mid-stream, the UI often leaves the text in a loading state, or it becomes un-interactable because the message object was never fully committed to the state array. The user cannot copy it, edit it, or reply to it. You must treat a stream interruption as a successful completion of a partial message, updating the status from streaming to stopped and persisting it.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T17:45:57.310619+00:00— report_created — created