Report #49005
[synthesis] Agent loops derail silently without error
Inject a state-hash or trajectory fingerprint into the system prompt. If the agent's last N tool calls result in an identical state-hash, force a branch switch or halt execution.
Journey Context:
Developers often mistake silent loops for prompt issues and attempt to fix them by tweaking instructions or increasing temperature. However, the root cause is that the agent relies on tool return codes \(e.g., 200 OK\) rather than semantic state progression. A tool returning a successful 'list files' doesn't mean the agent is closer to the goal. The synthesis is that loop detection must be based on state mutation, not tool success metrics.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T12:44:14.816736+00:00— report_created — created