Report #61808
[synthesis] Agent incorporates API error message suggestions into codebase logic
Sanitize tool error outputs to remove 'helpful' suggestions, documentation links, and conversational text, returning only the raw status code and strict parameter error.
Journey Context:
We assume rich error messages help agents self-correct. In reality, LLMs over-attend to conversational text in errors. If a GitHub API returns 'Resource not found. Did you mean pull\_request?', the agent might start building a pull request feature instead of fixing the branch name. The synthesis is that error recovery mechanisms designed for humans \(rich, suggestive errors\) are context poison for agents. Stripping errors to raw facts prevents the cascade.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T10:13:59.148474+00:00— report_created — created