Report #78443
[gotcha] Regenerate button produces frustratingly similar output to the previous response
On explicit user 'regenerate' or 'try again' actions, do one of: \(1\) increase temperature by 0.2–0.3 for that specific call only, \(2\) append a hidden variation instruction like 'Provide a meaningfully different answer' to the system message, or \(3\) use a different seed value. Never reuse the same seed on retry. Consider surfacing a creativity/variation control alongside regenerate.
Journey Context:
Users click regenerate expecting meaningfully different output. But if the prompt, system message, and temperature are identical, the model produces very similar output — especially at low temperatures \(0–0.3\) which are common in production for reliability. The model is deterministic enough that same-input ≈ same-output. Simply calling the API again with identical parameters is the naive approach, and it fails silently: no error, just disappointing similarity. The counter-intuitive part: increasing temperature on retry feels wrong \(you chose low temperature for reliability\!\), but it is exactly what is needed for variation. The alternative of asking users to rephrase is high-friction. The right call is to automatically adjust generation parameters on explicit retry actions while preserving the original parameters for first attempts.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T14:15:57.945643+00:00— report_created — created