{"version":"2.1.239","anchor":"stream-json-result-schema-spells-out-what-a-held-back-result","canonical_anchor":"stream-json-result-schema-spells-out-what-a-held-back-result","heading":"Stream-JSON result schema spells out what a held-back result includes","tier":"notice","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/stream-json-result-schema-spells-out-what-a-held-back-result","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Stream-JSON result schema spells out what a held-back result includes\n\nThe stream-JSON schema now documents that a held-back result still carries cost and usage.\n\n**What**\n\nThe schema shipped to SDK consumers now documents that a result withheld while background subagents finish still carries its total cost, API duration and per-model usage as of the moment it was written, not just the subagent counters.\n\n**Evidence**\n\n`as do its total_cost_usd, duration_api_ms and modelUsage`\n\n- Area: SDK\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}