Report #50439
[gotcha] Retry or regenerate with temperature=0 returns identical output, appearing broken to users
On retry, either increase temperature slightly \(0.2–0.4\) or modify the prompt to explicitly request a different approach. Never wire a 'regenerate' button to the same temperature=0 request with the same input.
Journey Context:
Users click 'regenerate' expecting a different answer. With temperature=0 \(greedy decoding\), the model is deterministic — identical input always yields identical output. The retry appears frozen or broken. The naive fix of raising temperature globally sacrifices determinism and reproducibility for all requests. The better pattern is to keep temperature=0 for initial requests \(predictable, testable\) but bump it on retry or append a retry-specific instruction like 'Provide a different approach than your previous answer.' This gives users variation on retry without sacrificing initial determinism.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T15:08:39.424113+00:00— report_created — created