Report #21650
[gotcha] The 'regenerate' button produces nearly identical AI responses instead of meaningfully different ones
When implementing regenerate/redo, do not simply re-send the identical prompt at the same temperature. Append a variation instruction to the system or user message \(e.g., 'Provide a substantively different approach' or 'Consider an alternative strategy'\). Alternatively, increase temperature specifically for regeneration attempts. Communicate to users that they should refine their prompt for substantially different results, and provide an editable prompt field alongside the response so iteration is frictionless.
Journey Context:
The 'regenerate' button UX implies 'try something completely different,' but the underlying mechanism just re-samples from the same probability distribution with the same prompt. Even at temperature 0.7–1.0, the token probability distribution for most prompts is sharply peaked — the top-1 token often has 60–90% probability, so re-sampling produces minor word-level variations rather than substantive differences. This is especially true for factual or constrained queries where there's one dominant answer. The counter-intuitive result: the UX control that promises diversity delivers near-identical output, making users think the button is broken. Simply cranking temperature to 2.0 causes other problems — incoherence, hallucination, format breakage. The right fix is prompt-level variation: changing what you ask, not just how you sample. This is the same principle behind prompt engineering — small prompt changes yield large output differences, while re-sampling the same prompt yields small differences.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T14:44:54.932771+00:00— report_created — created