Why does your agent still give different answers at temperature 0?
Summary
Setting temperature to 0 does not guarantee deterministic tool calls in agents due to batched inference causing floating-point reduction order shifts, leading to token flips and different actions under load.
Similar Articles
Same agent, same prompt, different runs. Which output do you ship?
The author observes that running the same task with Claude Code across different sessions yields varying decision patterns, making it hard to choose outputs that are safe to ship, and highlights the lack of tooling for evaluating agent decision profiles.
@jianxliao: How do we make agents deterministic?
A tweet by @jianxliao raises the question of how to make AI agents deterministic, sparking discussion on reliability and safety.
Your agent gets dumber the longer a session runs
The article discusses how AI agent performance degrades over long sessions due to context window clutter from raw history, tool outputs, and repeated reasoning, and suggests solutions like summarizing old turns and trimming tool outputs to extend useful run length.
Same agent, same task, wildly different costs per session?
A discussion on AI agent observability highlights unpredictable cost variations and dangerous failure modes like unauthorized database deletes, prompting questions about production handling strategies beyond basic logging.
Your coding agent didn't get worse. You just never measured the first version.
The article argues that perceived degradation in coding agents is often due to untracked changes in agent instances and configuration rather than the underlying model itself, highlighting a critical lack of baseline measurement in current AI agent workflows.