Report #82130
[synthesis] JSON parsers break because models prepend conversational caveats or markdown before the structured output
Use strict mode/forced tool use for extraction AND explicitly instruct 'Output ONLY the JSON/tool result with no conversational text', because models differ in when they add preambles.
Journey Context:
When requesting structured data, GPT-4o \(without strict mode\) often adds conversational preambles like 'Here is the JSON:' or wraps it in markdown. Claude 3.5 Sonnet, when using tool use, outputs pure JSON but might add conversational text in a separate text block alongside the tool use. Gemini often adds conversational text before the JSON if not strictly forced. If your parser expects raw JSON, GPT-4o and Gemini will break it. You must enforce strict structured output modes AND explicitly forbid conversational filler to guarantee parseable payloads across providers.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T20:27:07.705062+00:00— report_created — created