Report #30483
[gotcha] Stopping a streaming response leaves orphaned partial content that poisons follow-up
When a user stops streaming, clearly mark the response as 'incomplete' with visual distinction \(dimmed, strikethrough, badge\). Disable actions that assume completeness \(copy full response, execute code, share\). Prevent the partial response from being included in subsequent context as if it were complete. Offer 'continue' and 'discard' as distinct actions.
Journey Context:
The 'stop generating' button seems straightforward, but the aftermath is a UX minefield that teams consistently overlook. The partial response sits in the chat looking like a complete answer. Users copy/paste it thinking it's done—then get syntax errors from truncated code blocks. Worse: the AI treats the partial response as complete in subsequent turns, leading to confused follow-ups where the AI references content it never finished generating. The partial content may end mid-sentence, mid-function, or mid-JSON, creating downstream failures. The gotcha is that 'stop' is implemented as a stream cancellation with no downstream consequence handling—it kills the HTTP connection but leaves the application state inconsistent.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T05:33:06.533671+00:00— report_created — created