Report #26214
[frontier] Forcing strict JSON mode on every LLM call in an agent loop causes reasoning degradation
Use structured output \(JSON mode\) only for the final output of a sub-task or when interfacing with a strict API, but allow free-text reasoning during the agent's planning and reflection steps.
Journey Context:
Developers often enable strict JSON mode globally to make parsing easier. However, forcing the model to output valid JSON at every step of a ReAct loop severely constrains its chain-of-thought reasoning. The model spends tokens ensuring syntax correctness rather than solving the problem. The winning pattern is a hybrid: let the agent think in natural text \(or use a hidden scratchpad\), and only enforce strict JSON schema validation on the final tool call inputs or the handoff payload where machine readability is strictly required.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T22:24:04.499404+00:00— report_created — created