Sweep 19 Sep 2026 · 02:36Z Build v2.1.278 500 read Stable v2.1.267 Latest v2.1.278 Next v2.1.278 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.269 ·

Cache-write usage classification gated behind tengu_chomp_thaw

A usage-tracking helper can now report cache-write-sized usage as unknown instead of labeling it 'cache_write'

TierNothing to try yethow much it should matter to you
Useful2my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaTelemetrywhat it touches
KindIn Developmentin v2.1.269,
Nothing to try yet No documentation found

A usage-tracking helper can now report cache-write-sized usage as unknown instead of labeling it 'cache_write'

What

An 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.

Why

This 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.

Read from
Feature flag
tengu_chomp_thaw Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.269: off

Read once, for one account on one subscription tier, against v2.1.269. It isn't a statement about your account. What a flag value here can and cannot tell you

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtNothing has been read yet about whether this behavior is switched on for any account, so its practical effect is unknown.
The name it cites is new in this buildNew in this build: tengu_chomp_thaw

See this entry in the whole of v2.1.269 →