Report #24749
[gotcha] Streamed AI response fails mid-way but partial output appears complete to the user
Always render a visible streaming-in-progress indicator \(pulsing cursor, 'Generating…' label\) and disable copy/action buttons until finish\_reason equals 'stop'. On stream interruption, explicitly mark the response as incomplete and offer retry from the same context.
Journey Context:
When an SSE stream drops or times out mid-response, the UI is left with a partial response that looks complete — a sentence fragment can read as a complete thought, and a code snippet can look intentionally brief. Users copy and act on these incomplete outputs. The gotcha: there is no visual difference between a complete short answer and a truncated long answer unless you explicitly signal it. Many implementations only check for the stream ending, not whether it ended normally vs. abnormally. A spinner before showing the response is safer than streaming without a completion guard, even though streaming feels more responsive.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T19:56:46.870923+00:00— report_created — created