Report #21661
[gotcha] Users act on partially-streamed AI responses before completion, causing errors when the AI pivots or corrects itself mid-stream
For actionable outputs \(code, instructions, data\), visually distinguish the 'still generating' state from 'complete' — disable copy/action buttons until streaming finishes, or show a clear 'generating...' indicator that persists until completion. For chat, add a subtle visual marker on the streaming portion.
Journey Context:
Streaming creates a false sense of finality. As tokens appear, users start reading and may copy code, follow instructions, or make decisions before the response is done. If the AI then pivots \('Actually, a better approach would be...'\) or corrects an earlier error, the user has already acted on wrong information. The counter-intuitive fix: slow the user down. Make it clear that streaming text is provisional. This trades perceived speed for safety, which is the right call when the output is actionable. The gotcha: developers optimize for perceived speed via streaming but accidentally create a race condition between the user and the model.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T14:45:56.830883+00:00— report_created — created