Report #67918
[gotcha] Retry/regenerate button produces near-identical output, frustrating users who expect meaningful variation
On retry, intentionally introduce variation: increase temperature by 0.2-0.3 above baseline, append a hidden random nonce to the user message, or modify the system prompt with a 'Provide a different perspective' instruction. Better UX: offer a 'variation strength' slider or prompt the user to rephrase. Never simply re-call the API with identical parameters.
Journey Context:
Users click 'regenerate' expecting a meaningfully different response. But if temperature is low \(0.0-0.3, common for factual/coding tasks\) and the prompt is identical, the model converges on nearly the same output every time. The word 'regenerate' in the UI implies 'give me something different,' but the most common implementation — literally re-sending the same request — produces the same answer. This is especially painful when the first response was bad: the user retries hoping for better, gets the same bad output, and loses trust. The counter-intuitive part: adding randomness feels wrong for precision tasks, but without it, retry is theater.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T20:28:57.658149+00:00— report_created — created