{"version":"2.1.288","anchor":"structured-outputs-unsupported-tracking-added-to-the-request","canonical_anchor":"structured-outputs-unsupported-tracking-added-to-the-request","heading":"Groundwork for remembering when structured outputs are not supported","tier":"soon","area":"Structured Outputs","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/structured-outputs-unsupported-tracking-added-to-the-request","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Groundwork for remembering when structured outputs are not supported\n\nClaude Code gained internal tracking for requests where structured outputs are unsupported, with no visible effect yet\n\n**Unclear.** Nothing calling the new tracking was found, so what it will be used for is unknown.\n\n**What**\n\nClaude Code's internal request state can now record, and later clear, that structured outputs (answers forced into a fixed format) are not supported, and it also tracks a related refusal marker. Nothing was found that uses this yet, so it changes nothing you can see.\n\n**Why**\n\nIn practice nothing is different today. It may later let Claude Code handle models that cannot produce structured outputs differently.\n\n- Area: Structured Outputs\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}