Report #81857
[synthesis] Agent output parser extracts wrong data from changed API responses without failing, causing downstream hallucinations
Replace lenient regex/JSON parsers with strict schema validation that throws hard errors on unexpected fields or structural changes, rather than returning empty/null values silently.
Journey Context:
To make agents robust, developers often write parsers that gracefully handle missing keys or malformed JSON by returning defaults or None. When an external API changes its response structure, the lenient parser extracts garbage or None, which the LLM then hallucinates around to fill the gaps. A hard fail on structural change is better than a silent degradation into hallucination.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T19:59:20.398252+00:00— report_created — created