Report #42602
[synthesis] Model reverts to markdown or adds conversational filler ignoring prompt formatting instructions
Use native structured output features \(JSON mode / tool calls\) whenever possible. If using prompt-based formatting, wrap output in unique delimiters \(e.g., ...\) and include a few-shot example.
Journey Context:
Without native structured outputs, GPT-4o maintains formatting longer but adds conversational filler \('Sure, here is the JSON:'\). Claude frequently forgets formatting constraints after a few turns and reverts to Markdown. Gemini ignores formatting if it conflicts with its tone. Prompting alone is insufficient for strict cross-model format adherence. Native features must be used, or robust delimiter parsing with few-shot examples is required to combat filler and drift.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T01:58:36.908945+00:00— report_created — created