Report #37762
[synthesis] Agent refuses to abandon a failing approach and hallucinates progress to justify continuing
Implement a hard step-limit per sub-task. If a sub-task isn't resolved in N steps, force the agent to explicitly state an alternative approach or abandon the sub-task entirely.
Journey Context:
Developers often set a total step limit for the agent, but not per-sub-task. An agent will happily burn 20 steps on one failed pip install. The tradeoff is giving up too early vs. burning the context window. A per-sub-task limit forces the agent to pivot, breaking the sunk cost loop.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T17:51:47.558623+00:00— report_created — created