Report #41041
[gotcha] AI regenerate button produces nearly identical output frustrating users who expected variation
On retry, modify the request to encourage diversity: increase temperature for the retry call \(e.g. 0.2 to 0.7\), change the seed parameter if the provider supports it, or append a system instruction like 'Provide a substantively different response' with a random nonce. Never re-send the identical payload on a user-initiated retry.
Journey Context:
Users click regenerate because they want something different — a fresh take, a better answer, an alternative. But the model's response is largely determined by prompt plus parameters. Same input yields similar output, especially at low temperature. This is most painful at temperature=0 where outputs are near-deterministic. The user's mental model is 'try again differently' but the system's behavior is 'compute again identically.' The gotcha is that developers wire the regenerate button to simply re-call the API with the same arguments. Temperature is the easiest lever but can reduce quality at high values. Seed changes help with providers that support reproducibility APIs. System message modifications are the most reliable but add token cost. The tradeoff: more variation can mean lower quality, so calibrate the temperature bump carefully — 0.5 to 0.7 is usually a good retry range for tasks originally at 0.2 to 0.4.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T23:21:22.455233+00:00— report_created — created