Report #65855
[gotcha] Streaming AI responses create false confidence in completeness — users act on partial output
Disable action buttons \(copy, submit, execute\) and show a persistent 'still generating' indicator until the stream terminates with a done signal. Never surface affordances that imply the response is final while tokens are still arriving.
Journey Context:
Token-by-token streaming creates narrative momentum: users start reading and mentally check out before the response finishes. Caveats, corrections, and disclaimers that appear at the end are missed entirely. Teams often enable copy/submit actions as soon as text appears, assuming users will wait — they won't. A streamed response that says 'The best approach is X... \[still generating\] ...however, X has a critical security flaw, use Y instead' will get users committing to X before Y appears. The stream's done signal \(e.g., finish\_reason: 'stop'\) is the only reliable indicator of completeness. Treat in-progress streams as loading states, not readable states.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T17:01:18.131916+00:00— report_created — created