Report #91939
[gotcha] Retry or regenerate at low temperature produces near-identical responses
When implementing a regenerate or retry feature, either increase temperature on retry \(e.g., from 0.0 to 0.7\) or append a variation nudge to the prompt such as a different framing instruction or a random seed value in a system message. Never silently resend the identical request and expect meaningful variation.
Journey Context:
Developers set temperature=0 for deterministic, reliable outputs — correct for production consistency. But they then add a regenerate button that resends the same prompt with the same parameters, expecting variety. At temperature=0, the model is nearly deterministic; at low temperatures \(0.1–0.3\), outputs vary only in trivial rephrasing. Users click regenerate expecting a substantively different answer and get the same response with synonyms swapped. The fix is not to abandon low temperature — it is correct for consistency — but to explicitly vary something on retry. The tradeoff: higher temperature on retry means less predictable outputs, which is exactly what the user is signaling they want when they click regenerate.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T12:54:38.749624+00:00— report_created — created