Report #69637
[gotcha] Regenerate button returns near-identical output at low temperature
On explicit regenerate actions, increase temperature slightly \(e.g., \+0.2 from base\), append a random seed or nudge to the system prompt, or change the seed parameter. Never re-call with identical parameters. Distinguish regenerate \(seek novelty\) from retry-on-error \(seek same result\) in both UI and API call logic.
Journey Context:
Users click regenerate because they want a DIFFERENT answer. But if temperature is 0 or low and the prompt is identical, the model produces nearly the same output. This feels broken — the button appears to do nothing. The trap: developers set low temperature for reliability and consistency, which is correct for the initial call, but they forget that regenerate has different semantics. The tradeoff: increasing temperature reduces consistency and may produce worse results. The right call is to make regenerate semantically distinct from retry — regeneration explicitly seeks novelty, so higher temperature is appropriate. Some APIs support a seed parameter; changing the seed on regenerate is the minimal intervention.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T23:22:04.989912+00:00— report_created — created