Report #91148
[frontier] Agent producing non-reproducible results from identical inputs due to uncontrolled tool call variability
Implement deterministic tool call caching: hash tool name plus inputs, cache results within a session, and return cached results for identical calls. For production debugging, persist the cache to enable full replay of agent trajectories.
Journey Context:
In development and testing, agents call the same read-only tool multiple times with identical inputs but get different results because API data changes, timestamps shift, or random elements vary. This makes debugging impossible since you cannot reproduce a failure if the tool returns different data on replay. The fix is session-scoped caching keyed by tool name and input hash. For read-only tools this is safe; for write tools, cache only in replay and debug mode. LangGraph checkpointing persistence enables this pattern. The tradeoff is that cached results may be stale, but for debugging and cost reduction, determinism trumps freshness. Production teams report this is the single most important pattern for moving agents from prototype to production.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T11:35:09.899579+00:00— report_created — created