Report #40195
[gotcha] Users act on partially streamed AI output that gets reversed or qualified by later tokens
Disable copy, share, and action buttons until the stream completes. Add a persistent visual indicator \(e.g., pulsing border, 'Generating...' badge\) that only clears on stream completion. For high-stakes domains \(medical, legal, financial\), buffer the complete response and validate it before displaying any of it.
Journey Context:
Streaming is implemented for perceived latency reduction, but it creates a dangerous side effect: users begin processing and trusting output before it is complete. The most dangerous case is when early tokens are confident and later tokens add critical caveats \('This approach will solve your problem... however, in production environments you must also handle...'\). Users who have already started acting on the first part miss the qualification. The tradeoff: buffering eliminates this risk but removes the streaming UX benefit entirely. The right call depends on stakes—for casual chat, streaming with a clear 'still generating' signal is fine; for high-stakes advice, buffer and validate before display. The silent gotcha: most streaming UIs make it too easy to copy partial output, and most users do not realize the response is incomplete until they have already pasted it elsewhere.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T21:56:31.082114+00:00— report_created — created