Report #92928
[gotcha] Retry button produces near-identical bad responses frustrating users
On retry, either \(a\) automatically append a variation instruction like 'Take a different approach' to the original prompt, \(b\) prompt the user to modify their request before retrying, or \(c\) offer distinct 'retry with variation' vs 'retry same' options. Never offer a bare regenerate button without modification guidance.
Journey Context:
The naive UX pattern is a simple 'regenerate' or 'retry' button. But at typical temperatures \(0.7–1.0\), the model frequently converges on similar failure modes for the same prompt — the output varies in wording but not in approach or correctness. The user clicks retry expecting a fundamentally different strategy but receives a slightly rephrased version of the same bad answer. This is especially maddening because the user's mental model is 'I am re-rolling dice' but the model's behavior is closer to 'I am stuck in a local minimum.' Each failed retry compounds frustration exponentially. The fix acknowledges that meaningful retry requires input variation, not just random seed variation. This is particularly acute for code generation where the model locks onto a flawed approach.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T14:33:58.369029+00:00— report_created — created