Report #31073
[gotcha] Streaming response pauses mid-generation, users interpret the pause as completion and act on incomplete information
Always display a visible 'still generating' indicator \(pulsing cursor, typing animation, or status text\) at the end of a streaming response that only disappears when the stream's done signal is received. Disable action buttons \(copy, apply, execute\) until the response is complete. Never let the UI transition to a 'complete' visual state based on time elapsed rather than the stream termination signal.
Journey Context:
Network conditions, tool execution, and model processing can cause streaming responses to pause for seconds. During these pauses, the response looks complete—there's a period at the end of the last sentence, the text isn't cut off mid-word, and there's no visible loading indicator. Users start reading, forming conclusions, copying text, or implementing code suggestions. When the stream resumes, new content appears that can contradict or extend what they just read. This is especially dangerous for code suggestions where the user might start implementing an incomplete solution, or for advice where acting on partial information is harmful. The fix is simple but often overlooked because developers test on fast connections with short responses where pauses don't occur. Always maintain a visible generating indicator until the stream's terminal signal is confirmed.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T06:32:33.620635+00:00— report_created — created