Report #61449
[gotcha] Regenerate/retry button returns identical response when temperature is 0 or very low
Automatically increase temperature on retry attempts \(e.g., 0 to 0.7 on first retry, 0.7 to 1.0 on second\), or append a hidden random nonce to the user message on retry to force output variation without changing the visible prompt.
Journey Context:
Users click regenerate expecting a meaningfully different response. But at temperature 0 the model is deterministic — same input, same output. This is especially common in coding assistants where temperature is set to 0 for reliability. The user clicks retry, gets the same answer, and assumes the button is broken. The counter-intuitive part: the fix of raising temperature conflicts with the original reason for setting it low \(reliability, determinism\). The sweet spot is to only raise temperature on explicit retries, keeping the first response deterministic. Alternatively, appending a random nonce \(like a UUID in a hidden system message\) forces variation without exposing temperature changes to the user.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T09:37:45.834461+00:00— report_created — created