Report #82537
[gotcha] Retry/regenerate button returns nearly identical response, frustrating users who expected variation
On retry, either increase temperature slightly \(e.g., \+0.2 from default\), append a system nudge like 'Provide a different approach to this question,' or prompt the user to modify their query before retrying. Track retry count and escalate the nudge on repeated attempts.
Journey Context:
Users click 'regenerate' expecting meaningfully different output, but at default temperature the model frequently converges to similar responses — especially for factual or well-structured queries where the answer space is narrow. The retry UX becomes a frustration loop. Simply increasing temperature globally risks hallucination. The targeted approach — nudging variety only on retry — balances variation with reliability. Another pattern: after 2 identical retries, surface a UI prompt asking the user to specify what they want changed \('more concise?', 'different approach?'\), turning the blind retry into a directed refinement.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T21:07:35.932984+00:00— report_created — created