Report #64325
[gotcha] Regenerate button replaces previous AI response destroying the user reference point
Implement retries as branching variants \(like a git branch or version history\) rather than in-place replacements, allowing users to compare the old and new responses side-by-side.
Journey Context:
Standard web UX dictates 'update in place' for refreshes. But LLM outputs are non-deterministic. When a user clicks regenerate because the first answer was almost right, replacing it entirely causes anxiety and loss of good partial info. Branching preserves the probabilistic nature of the output.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T14:27:38.400674+00:00— report_created — created