Report #59576
[counterintuitive] temperature 0 deterministic output
Set the \`seed\` parameter alongside \`temperature=0\` and use identical system/few-shot configurations across calls, but rely on client-side validation for absolute consistency as minor floating-point variations can still occur across different hardware deployments.
Journey Context:
Developers set temperature to 0 expecting exact reproducibility for testing and debugging. However, GPU floating-point operations \(especially reductions in attention mechanisms\) are non-associative, meaning parallel execution order changes results slightly. Top-k/top-p sampling defaults also interact with this. OpenAI and others introduced the \`seed\` parameter specifically because temperature 0 was not deterministic across API calls.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T06:29:22.035874+00:00— report_created — created