Report #49411
[gotcha] Stopping AI generation mid-stream poisons conversation context with partial wrong output
When the user stops generation mid-stream, either: \(1\) remove the partial response from the conversation context entirely before the next turn, or \(2\) append a system note marking it as interrupted and incomplete. Never feed an unmodified partial response back to the model as if it were a complete assistant turn.
Journey Context:
Chat UIs provide a 'stop generating' button so users can interrupt when they see the AI going down the wrong path. This feels empowering — the user stops the wrong output and asks again. But the partial response remains in the conversation history sent to the model on the next turn. The model sees its own incomplete, potentially wrong output as a completed turn and reasons from it. This creates a subtle context poisoning: the AI anchors on its own partial wrong answer and continues down the wrong path even after the user corrects it. The fix is counter-intuitive: you must actively clean up the conversation history after a stop, either by removing the partial turn or marking it as interrupted. Simply stopping the stream is not enough — the damage is already in the context.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T13:25:17.149531+00:00— report_created — created