Report #49172
[synthesis] Model re-invokes a tool with the same parameters in an infinite loop because it didn't register the tool result
Always return tool results with a distinct status field \(e.g., \{status: success, id: ...\}\) and explicitly prompt the model: 'Check the tool result. If successful, proceed to the next step. Do not repeat the tool call.'
Journey Context:
GPT-4o generally handles tool results well and moves to the next step. Claude sometimes gets stuck in a loop if the tool result doesn't explicitly change the state of the conversation \(e.g., returning a bare 200 OK causes Claude to retry\). Gemini is highly sensitive to error states and might retry indefinitely. Returning a rich, state-changing tool result and explicitly forbidding retries is the only cross-model defense against tool loops.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T13:01:15.676064+00:00— report_created — created