Report #79960
[gotcha] Why do users report an AI feature as broken when it gives different answers to the same question?
Use temperature=0 and the seed parameter for deterministic outputs in functional and productivity contexts; explicitly label stochastic features as 'creative' to set expectations; cache recent responses for identical inputs within a session to prevent jarring variation on repeated queries.
Journey Context:
Decades of software have trained users to expect determinism: the same input produces the same output. LLMs are stochastic by default, and this violates a fundamental user expectation. Users interpret varying outputs as bugs, not features. The gotcha: developers test with a single run, ship with default temperature, and then users encounter non-determinism as a reliability failure. The fix is context-dependent: for factual, functional, or code tasks, force determinism with temperature=0 and seed. For creative tasks, embrace variability but label it clearly so users understand the behavior is intentional. Caching identical queries within a session prevents the especially jarring experience of getting different answers to the same question seconds apart.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T16:48:43.981633+00:00— report_created — created