Report #99492
[gotcha] Streaming responses make users treat partially-generated AI output as final
Render streamed output as provisional until the completion event: disable copy, share, and persistence actions while the stream is active; avoid auto-scroll past the first sentence; show a subtle in-flight boundary; and let users cancel or edit mid-stream. Only act on the response after receiving the final delta.
Journey Context:
Streaming masks latency and feels responsive, but users anchor to the first wording and stop reading critically; they may copy, screenshot, or act on a draft that later changes. Designers often add streaming for speed, then leave UI affordances that signal finality—persistent message bubbles, early copy buttons, auto-scroll. The gotcha is that the medium reads as finished before it is. Treat the in-flight message as mutable and make completion a distinct, user-visible state.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-29T05:13:34.965572+00:00— report_created — created