Report #87231
[gotcha] Regenerate button destroys the previous AI response instantly before new one generates
Keep the previous response accessible via a branching UI \(toggle arrows\) while the new response streams in, or at least delay removal until the new stream starts yielding tokens to avoid a blank layout shift.
Journey Context:
Users hit 'regenerate' to see an alternative, but if the network lags, the screen flashes blank or collapses, causing a jarring layout shift. If the new response is worse, they've lost the old one. Branching UI prevents this by treating regenerations as parallel timelines, but even a simple delayed replacement prevents the jarring 'content disappearing' flash.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T05:00:29.621262+00:00— report_created — created