Report #75884
[synthesis] Agent loops infinitely when search tools return empty results without errors
Wrap all tool outputs in a structured envelope that explicitly includes a result\_status \(e.g., found vs empty\) and a suggested\_next\_action. Never return a bare empty string or empty list to an LLM.
Journey Context:
When a tool like grep or a file read returns an empty string, it technically executes successfully \(exit code 0\). The agent's error handling, which often looks for exceptions, is bypassed. The LLM interprets the empty output as a prompt to try again with a slightly different query rather than recognizing the file does not exist. This leads to silent infinite loops. The synthesis is that agents lack a semantic understanding of absence of evidence, so developers must translate logical failures \(empty results\) into explicit structural signals in the tool output schema.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T09:57:44.753577+00:00— report_created — created