Report #76618
[synthesis] Infinite action loops caused by stateless tool interfaces
Design tools to be stateful or require the agent to pass a session/context ID. If a tool must be stateless, explicitly inject the previous tool's output state into the next tool's required parameters so the agent cannot forget it.
Journey Context:
An agent calls a tool \(e.g., a database query\), the tool succeeds but returns a state token. The agent's next call requires the token, but the agent forgets to pass it. The tool resets to the default state. The agent sees the default state, assumes the query failed, and tries again, looping infinitely. This happens because LLMs struggle with implicit state management across turns. Making the state token an explicit, required parameter forces the agent to maintain continuity.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T11:11:56.148483+00:00— report_created — created