How do you trust an agent that answers differently each time?

Build trust on calibrated reliability rather than a single good answer, and people can rely on an agent that is not deterministic. The goal is appropriate reliance, not blind faith or blanket doubt.

B

Balagei G Nagarajan

3 MIN READ


A person calibrating trust in an agent whose answers vary run to run
So a high-stakes decision-maker who watches an agent contradict itself is not being irrational by hesitating.
— from “How do you trust an agent that answers differently each time?”

Key facts.

  • Lee and See's work on trust in automation defines appropriate reliance: trust calibrated to a system's actual reliability, neither over-trust nor reflexive distrust. source
  • Thinking Machines Lab's "Defeating Nondeterminism in LLM Inference" shows model outputs can differ run to run even at temperature zero, so identical inputs do not guarantee identical answers. source
  • Reviews of automation bias show miscalibrated trust produces predictable failures: complacency when people over-trust, aversion when they under-trust. source
  • A newer model still varies at temperature zero, so trust rides a track record, not one demo and the cost lands where you skip it. (source)

Why is non-determinism a trust problem, not just a technical one?

People build trust from consistency. A colleague who gives the same sound answer every time earns reliance; one who answers differently each time, even when often right, makes us wary. An agent is the second kind by default. The Thinking Machines result is the uncomfortable proof that this is structural, not a tuning oversight: the same prompt can yield different outputs even at temperature zero. So a high-stakes decision-maker who watches an agent contradict itself is not being irrational by hesitating. They are responding to genuine variability.

The way through is the human-factors answer, not a promise of determinism you cannot keep. Trust should be calibrated to the agent's measured reliability on the specific kind of work, so the person knows where to rely and where to verify. That requires showing a track record rather than a demo and designing the agent so its behavior on a given situation is consistent enough to earn calibrated trust, even if the raw tokens vary.

A calibration curve mapping appropriate reliance to measured reliability

How do you make trust calibrated, not blind?

ApproachBlind faithBlanket distrustCalibrated reliance
BasisOne good answerOne bad answerMeasured track record
Where usedEverywhereNowhereWhere it is reliable
OutcomeSilent failuresWasted agentValue with safety

Calibrated trust needs consistent behavior at the level people actually care about, which is the situation, not the token stream. VibeModel is the Pattern Intelligence Layer because it makes the agent handle the same situation the same correct way every time, turning raw non-determinism into pattern-level consistency. That is what lets a high-stakes team extend appropriate reliance to an agent that, underneath, never answers in exactly the same words twice.

Frequently asked questions

Can you make an agent fully deterministic?
Not reliably. Work like Thinking Machines Lab's shows outputs can vary even at temperature zero, so trust has to be built on calibrated reliability, not on identical answers.

What is appropriate reliance?
Trusting the agent where its measured reliability is high and verifying where it is not, instead of trusting everything or nothing.

How do you show reliability to skeptics?
With a track record on their kind of work, not a demo. Calibration comes from evidence over time.


Share this post

Join the discussion

Have a take, a war story, or a question? Sign in with GitHub to comment and react. Comments are powered by GitHub Discussions, ad-free and yours to moderate.

Continue Reading

Find where your agent breaks, before you build it

Faultmap maps where your agent will fail from the goal and your data, then hands you the first test suite it has to pass.