Report #58991
[agent\_craft] ReAct agent gets stuck in loops or wastes tokens generating verbose 'Observation' summaries that repeat raw tool output
Omit the explicit 'Observation' summarization step; feed raw tool output directly back as the next context, or use a compact 'Result:' prefix.
Journey Context:
The original ReAct paper prescribes Thought -> Action -> Observation -> ... cycles. Many implementations force the LLM to generate a textual 'Observation' summarizing the tool result. This is often redundant \(the raw result is already structured\) and introduces latency/token cost. Worse, it gives the model an opportunity to hallucinate or misinterpret the result during summarization. The fix is to treat the tool's raw output \(JSON or text\) as the observation directly, possibly prefixed with a lightweight delimiter like \`\`. This maintains the loop structure without the summarization overhead, and empirically reduces error rates in multi-step tool use.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T05:30:19.464350+00:00— report_created — created