Report #92013
[synthesis] Agent receives a verbose error trace and abandons the user goal to debug the tool's internal state
Sanitize tool error outputs before feeding them back to the agent. Provide only the actionable, high-level error message. If a stack trace is needed, summarize it or place it in a separate, on-demand context.
Journey Context:
LLMs are trained to be helpful and fix errors. When presented with a complex stack trace, the agent's RLHF tuning overrides the high-level goal, causing it to pivot to debug the error mode. It will spend its entire context window trying to fix an internal tool error \(which it cannot fix\) rather than trying an alternative approach to achieve the user's goal. Raw error traces act as a context poison and a goal-derailment trigger.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T13:02:12.609647+00:00— report_created — created