Report #74333
[gotcha] Regenerate/retry button produces nearly identical bad responses
When implementing retry or regenerate, never silently re-submit the identical prompt with identical parameters. Instead: \(a\) bump temperature by 0.1-0.2 per retry attempt, \(b\) append a hidden system instruction like 'Provide a different approach to this question' on retries, or \(c\) prompt the user to modify their query before retrying. Option \(b\) is the most reliable for producing meaningfully different outputs.
Journey Context:
The user clicks 'regenerate' expecting a meaningfully different answer. But LLMs with the same input and same temperature produce very similar outputs — this is by design for reproducibility. The regenerate button creates an implicit contract: 'I'll try a different approach.' Silently re-running the same prompt violates this contract. Engineers often set temperature=0 for reliability, which makes retries almost identical. The common mistake is thinking 'the model is stochastic, so it'll naturally produce different output' — at low temperatures, the variance is negligible. The fix treats retry as a distinct interaction type. The tradeoff: slightly less predictable output on retries vs. actually delivering on the user's expectation of a different answer.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T07:22:02.888811+00:00— report_created — created