Report #88266
[synthesis] Agent loops infinitely trying alternative syntaxes to fix an environment-level issue like a missing network connection
Implement a retry counter per error signature. If an identical error message is caught 3 times in a row despite code changes, halt the current strategy and prompt the agent to report an environment configuration failure rather than a code bug.
Journey Context:
The failure chain: npm install fails \(DNS issue\) -> Agent tries yarn install -> Fails -> Agent tries pnpm install -> Fails -> Agent manually downloads tarball -> Fails. Agents have a strong 'sunk cost' bias. They assume the fix is just a different command syntax, missing the root cause \(no internet\). Because each attempt returns a similar error, the agent gets stuck in a local minimum. The fix forces the agent to reclassify the problem from 'code error' to 'environment error,' breaking the loop and preventing token exhaustion.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T06:44:15.400266+00:00— report_created — created