Report #78301
[synthesis] Agent patches code to suppress error messages instead of fixing root cause logic
Strip or summarize the raw stack trace in the prompt, and explicitly instruct the agent to explain the state that led to the error before writing a fix; ban broad exception blocks in generated code.
Journey Context:
LLMs are highly biased toward the exact text of an error message. If the error says 'IndexError', the agent will add an \`if len\(list\) > 0\` check, even if the real bug is that the list was populated with the wrong data upstream. The error message becomes a distraction. By forcing the agent to reason about the state and banning error suppression patterns, you shift the attention from the symptom to the disease.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T14:01:28.127190+00:00— report_created — created