{"version":"2.1.277","anchor":"new-sdk-query-usagecost-fields-get-detailed-docs","canonical_anchor":"new-sdk-query-usagecost-fields-get-detailed-docs","heading":"New SDK query() usage\/cost fields get detailed docs","tier":"internal","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/new-sdk-query-usagecost-fields-get-detailed-docs","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### New SDK query() usage\/cost fields get detailed docs\n\nSDK docs now spell out that query() usage and cost totals accumulate across turns and reset on \/clear\n\n**What**\n\nThe descriptions for the SDK's `query()` result fields covering model usage and total cost have been expanded. They now explain that per-model token totals (`modelUsage`) and the cumulative estimated cost (`totalCostUsd`-like field) both accumulate across turns within a streaming session, and reset when `\/clear` is used to start a new conversation.\n\n**Why**\n\nThis clarifies for SDK users exactly what window of activity these numbers cover, so a running cost or usage total isn't mistaken for a single-turn figure or misunderstood after a `\/clear`.\n\n- Area: SDK\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}