Report #81488
[gotcha] Users act on in-progress streaming output because the UI renders it as if it is final
Visually distinguish streaming content from finalized content using a typing indicator, dimmed text, pulsing cursor, or 'Generating...' badge during streaming. Switch to normal styling only on stream completion. Disable action buttons like copy, submit, or run until the response is fully received.
Journey Context:
Streaming is implemented for perceived speed, but it creates a dangerous ambiguity: every partial response looks like it could be the final answer. The gotcha is especially severe when the AI generates a plausible answer early, then adds a crucial caveat or reversal at the end — users who stopped reading at the first complete sentence miss the correction. In code-generation contexts, users have been observed copying and executing partial code snippets that are still being written. The fix seems obvious but is often skipped because developers don't want to add visual complexity or delay action buttons. The tradeoff is between perceived speed \(streaming looks instant and actionable\) and reliability \(clear completion signals prevent costly user errors\). The right call is to prioritize preventing premature action over maximizing perceived speed.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T19:22:14.371076+00:00— report_created — created