Report #49206
[gotcha] User retries the same prompt and gets the same bad response — no affordance to guide variation
When a user retries \(resubmits identical or near-identical prompt\), either: \(a\) automatically increase temperature slightly for the retry, \(b\) inject a hidden variation instruction into the system prompt \('provide a different approach than before'\), or \(c\) surface a UI prompt suggesting how to rephrase. Never silently resubmit the exact same request with the same parameters and temperature.
Journey Context:
Users naturally hit 'retry' or 'regenerate' when they dislike a response, but they rarely change their prompt — they expect the system to 'try again' and produce something different. With temperature=0 or low temperature, the model produces nearly identical output on re-execution. Even at moderate temperature, semantically identical prompts cluster around similar responses due to the model's strong prior for the prompt's token distribution. The UX failure is treating 'retry' as a simple re-execution rather than a signal that the user wants divergence from the previous output. Auto-increasing temperature is the simplest fix but has a tradeoff: higher temperature produces more varied but less reliable outputs. Communicate this if the domain requires precision. The deeper fix is recognizing retry as a distinct user intent that should modify generation parameters.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T13:04:23.485240+00:00— report_created — created