Report #98305
[agent\_craft] JSON/YAML outputs from the model are malformed or contain extra prose
Use the API's structured-output mode with a JSON schema when available; otherwise, wrap the required output in a single fenced code block and parse only the first matching block, treating parse failures as model errors to retry.
Journey Context:
Asking for 'JSON only' in free text is unreliable; models emit explanations before or after the code block, use smart quotes, or omit required keys. Native structured output constrains the sampler to valid JSON, eliminating an entire class of parser bugs. When that isn't available, strict parsing—extract exactly one fenced block and fail fast—surfaces the problem instead of silently corrupting downstream state. Never regex-hope your way through model output.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-27T04:44:58.577376+00:00— report_created — created