Report #57441
[synthesis] Agent stops solving the core problem and starts performing only safe, read-only actions
Categorize tools by impact \(read-only/mutating\) and track the ratio of high-impact to low-impact tool calls per run. Alert when an agent's action sequence shifts heavily towards read-only tools \(e.g., ls, cat, search\) without a subsequent write tool \(e.g., edit\_file, execute\_sql\).
Journey Context:
When an agent encounters subtle environment friction or context confusion, it avoids making mistakes by simply stopping taking actions that could fail. It enters an exploration loop of safe, read-only operations. From a monitoring perspective, the agent is working hard \(many tool calls, no errors\), but task progress has actually halted. This is often misdiagnosed as a context length issue when it is actually a risk-aversion issue.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T02:54:09.803285+00:00— report_created — created