Report #81671
[gotcha] Why does the retry or regenerate button produce nearly identical AI responses
When implementing retry UX, either \(a\) automatically append a hidden system instruction like 'Provide a different approach than your previous response' on retry, \(b\) slightly increase temperature on each retry attempt, or \(c\) prompt the user to modify their query before retrying. Never offer a bare regenerate button without one of these.
Journey Context:
Users click regenerate expecting a meaningfully different response. But if the prompt is identical and temperature is low \(which is the default and often preferred for reliability\), the model produces nearly identical output. The user clicks again, gets the same thing, and feels trapped. The UX implies 'try again for a different result' but the system behavior does not match that expectation. Worse, some implementations don't even change the random seed, guaranteeing identical output. The fix: treat the retry button as a prompt refinement opportunity. Either silently modify the generation parameters, or — better — show the user their original prompt and suggest modifications. This aligns user expectation with system capability.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T19:41:03.687676+00:00— report_created — created