{"version":"2.1.269","anchor":"cache-write-usage-classification-gated-behind-tengu-chomp-th","canonical_anchor":"cache-write-usage-classification-gated-behind-tengu-chomp-th","heading":"Cache-write usage classification gated behind tengu_chomp_thaw","tier":"soon","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/cache-write-usage-classification-gated-behind-tengu-chomp-th","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Cache-write usage classification gated behind tengu_chomp_thaw\n\nA usage-tracking helper can now report cache-write-sized usage as unknown instead of labeling it 'cache_write'\n\n**Unclear.** Nothing has been read yet about whether this behavior is switched on for any account, so its practical effect is unknown.\n\n**What**\n\nAn internal helper called `lms` classifies each message's token usage into one of three buckets: \"uncached\", \"cache_write\", or unknown. A new setting can now change that classification so that usage which would normally be labeled \"cache_write\" is instead reported as unknown.\n\n**Why**\n\nThis affects internal usage accounting rather than anything visible in the chat itself, so most users won't notice a difference in day-to-day use.\n\n- Flag `tengu_chomp_thaw`: Not enough to say (read for one account on one subscription tier against v2.1.269; this account: no value returned, anonymous baseline: no value returned, compiled default: off)\n- Area: Telemetry\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}