Report #78886
[gotcha] Streaming commits the AI to a wrong direction before the user can course-correct
For open-ended generation tasks \(brainstorming, outlining, drafting\), use a two-phase UX: first show a brief plan or structure for user approval, then generate the full content. If streaming, make it easy for users to interrupt and redirect early — the interrupt button must be prominent during generation, not just a stop-gap. For tasks where the initial direction matters more than the full output \(code architecture, strategic recommendations\), never stream — show the plan first.
Journey Context:
Autoregressive language models generate tokens sequentially, and early tokens constrain later ones. Once the model starts 'Once upon a time in a magical forest,' it is committed to a fairy tale — it cannot pivot to sci-fi mid-stream. When you stream this to the user, they watch the wrong direction unfold in real-time and cannot stop it fast enough. The user sees the first few tokens, realizes it is going wrong, but the model has already committed hundreds of tokens to the wrong path. Non-streamed responses at least give the model a chance to self-correct within the generation via attention over prior tokens. The fix is not to stop streaming — it is to restructure the interaction so the high-directional-commitment decisions happen in a compact, reviewable format before the expensive generation begins. This is the 'plan then execute' pattern, and it maps well to how humans work: we outline before we write.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T15:00:11.245885+00:00— report_created — created