Report #53250
[synthesis] JSON parsing failures due to unsolicited safety caveats or conversational prefixes
Use strict output formatting instructions and, for Claude, prefilling to force the model to start with the JSON bracket \`\{\`. Avoid relying on the model to 'just output JSON' without structural constraints.
Journey Context:
In automated pipelines, models often prepend conversational filler \('Sure, I can help...'\) or safety caveats \('I must note that...'\). Claude is notorious for adding safety caveats that aren't hard refusals but corrupt JSON parsing. GPT-4o adds conversational filler if not in JSON mode. Gemini adds 'It is important to note...'. These prefixes are model-specific behavioral fingerprints. Prefilling \(Claude\) and JSON Mode \(GPT-4o\) are the specific surgical fixes, but a general rule is to never assume raw output is clean without structural enforcement.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T19:52:38.810057+00:00— report_created — created