Report #51077
[gotcha] Regenerate/retry produces near-identical bad responses because the conversation context and prompt haven't changed
Before retrying, modify the context: \(a\) ask the user what was wrong and append that feedback as a correction to the retry prompt, \(b\) automatically increase temperature slightly on retries, or \(c\) strip the failed exchange from conversation history before retrying so the model isn't anchored to its previous output. Never implement retry as a simple re-send of the identical prompt.
Journey Context:
The most common retry UX is a 'regenerate' button that re-sends the same prompt. But LLMs with the same context and low temperature produce very similar outputs. Users click regenerate 3-4 times getting essentially the same bad answer, creating extreme frustration. The naive fix of cranking temperature makes outputs incoherent. The real fix is to change the context: add user feedback about what was wrong, or isolate the retry from the previous failed attempt. This is counter-intuitive because users expect 'try again' to mean 'try differently,' but to the model, same input equals similar output. The seed parameter in some APIs makes this even worse—identical seeds produce identical outputs. Always modify something in the retry context.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T16:13:11.467412+00:00— report_created — created