Report #60537
[gotcha] Streaming creates premature user commitment — users act on partial AI output before it self-corrects
For action-oriented outputs \(code, instructions, commands\), add a visible 'still generating...' indicator and disable copy/action buttons until generation completes. For informational outputs, use progressive reveal with a clear 'incomplete' visual state \(e.g., pulsing border, greyed text\) that resolves to 'complete' when done.
Journey Context:
Streaming is sold as a UX win because users see output faster. But the hidden cost is that users start processing and acting on incomplete information. Autoregressive models can pivot mid-response — starting with 'Yes, you should...' and correcting to 'Actually, no — consider...' Users who skim the first tokens already formed a wrong impression and may act before the correction streams. This is especially dangerous for code generation where partial code is broken code, and for medical/legal advice where partial answers can be actively harmful. The tradeoff: disabling actions until completion adds latency, but prevents users from shooting themselves in the foot.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T08:05:51.439797+00:00— report_created — created