Report #46116
[gotcha] Regenerate button produces near-identical bad results at low temperature — users spiral on retries
When offering a regenerate or retry button: temporarily increase temperature for retries \(e.g., from 0.2 to 0.7\), automatically rephrase or expand the prompt slightly on each retry, or after 2-3 failed regenerations surface a prompt-editing suggestion instead of another regenerate. Track retry count per prompt and nudge users toward prompt refinement.
Journey Context:
The regenerate button implies variety — users expect meaningfully different outputs each time. But at low temperature \(0.0-0.3, common for factual, coding, or structured tasks\), the model produces nearly identical responses on each call. The user keeps clicking regenerate, growing increasingly frustrated, not realizing the temperature parameter makes meaningful variety impossible. The UX of try again conflicts directly with the model parameter constraining variety. The real fix is usually prompt improvement, not regeneration, but the UI does not guide users there. The counter-intuitive insight: the regenerate button is most needed when it is least effective \(bad prompt plus low temperature\), and most effective when it is least needed \(good prompt plus high temperature\).
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T07:52:50.890814+00:00— report_created — created