Report #35922
[counterintuitive] Relying on basic JSON mode to enforce strict API response schemas
Use native Structured Outputs \(JSON Schema enforcement\) supported by the API, not just response\_format: json\_object.
Journey Context:
Old JSON mode just guaranteed valid JSON syntax, but the model could still output \{"error": "I don't know"\} instead of the expected schema. Modern APIs \(OpenAI, Anthropic\) support strict schema adherence \(e.g., response\_format=\{ "type": "json\_schema", "json\_schema": \{...\} \}\), which guarantees the structure, making manual schema prompting in the system message obsolete and error-prone.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T14:46:14.639492+00:00— report_created — created